oodt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sheryl John <shery...@gmail.com>
Subject Re: Workflow instance error
Date Thu, 18 Aug 2011 01:25:18 GMT
I tried the first option and it worked after restarting the wmgr.
I had specified a wrong path to the repo and so, I guess that's why it
throwing these errors. But, I don't see any messages in the log files that
indicate the corruption.

Thanks!



On Wed, Aug 17, 2011 at 4:15 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> Hi Sheryl,
>
> It looks like your Lucene index for the Workflow Manager is corrupt. You
> can:
>
> 1. blow away $WMGR_HOME/repository/catalog/whatever you called it.
> 2. restart the WM
>
> Or, you can examine the index directory with Luke [1] and see if you can
> open it.
>
> Any log messages in the Workflow Manager log file that would indicate the
> corruption?
>
> Cheers,
> Chris
>
> [1] http://getopt.org/luke/
>
> On Aug 17, 2011, at 3:01 PM, Sheryl John wrote:
>
> > Hi Chris,
> >
> >
> > I'm getting the workflow error again with a different message:
> >
> > WARNING: Unable to index workflow instance:
> [717e7eb5-c91b-11e0-b089-51634b6a98fc]: Message: read past EOF
> >
> > And, when I tried removing the lock ( rm -rf
> /tmp/lucene-76ae6fd29a43a2046fb462e76a907e1d-write.lock ), and restarted the
> wmgr it shows the same error and the above lucene lock turns up again in
> /tmp.
> >
> >
> >
> > On Fri, Aug 12, 2011 at 6:32 PM, Mattmann, Chris A (388J) <
> chris.a.mattmann@jpl.nasa.gov> wrote:
> > Hey Sheryl,
> >
> > Thanks for your message. The first error is a temporary lock file left
> over by Lucene. This is seen from
> > time to time when using the LuceneWorklfowInstanceRepository. The
> simplest way to address it is to
> > rm -rf /tmp/lucene-76ae6fd29a43a2046fb462e76a907e1d-write.lock, and then
> run ./wmgr restart. You should
> > be good after that.
> >
> > HTH,
> > Chris
> >
> >
> > On Aug 12, 2011, at 5:25 PM, Sheryl John wrote:
> >
> > > Hi all,
> > >
> > > I am using the Workflow Manager to run some events, and it was working
> fine earlier today before I started getting some timed out lock warnings.
> > > I didn't update any part of my defined workflow, but I was away for a
> while before I restarted the wmgr. After starting off the wmgr-client, I got
> the below warnings:
> > >
> > >
> > >
> > > INFO: WorkflowManager: Workflow pythonWorkflow retrieved for event
> pythonWorkflow
> > > Aug 12, 2011 3:57:09 PM
> org.apache.oodt.cas.workflow.instrepo.LuceneWorkflowInstanceRepository
> addWorkflowInstanceToCatalog
> > > WARNING: Unable to index workflow instance:
> [682adca4-c536-11e0-a906-354a8363ecc7]: Message: Lock obtain timed out:
> Lock@/tmp/lucene-76ae6fd29a43a2046fb462e76a907e1d-write.lock
> > >
> org.apache.oodt.cas.workflow.structs.exceptions.InstanceRepositoryException:
> Unable to index workflow instance: [682adca4-c536-11e0-a906-354a8363ecc7]:
> Message: Lock obtain timed out: Lock@
> /tmp/lucene-76ae6fd29a43a2046fb462e76a907e1d-write.lock
> > >       at
> org.apache.oodt.cas.workflow.instrepo.LuceneWorkflowInstanceRepository.addWorkflowInstanceToCatalog(LuceneWorkflowInstanceRepository.java:462)
> > >       at
> org.apache.oodt.cas.workflow.instrepo.LuceneWorkflowInstanceRepository.addWorkflowInstance(LuceneWorkflowInstanceRepository.java:175)
> > >       at
> org.apache.oodt.cas.workflow.engine.ThreadPoolWorkflowEngine.persistWorkflowInstance(ThreadPoolWorkflowEngine.java:435)
> > >       at
> org.apache.oodt.cas.workflow.engine.ThreadPoolWorkflowEngine.startWorkflow(ThreadPoolWorkflowEngine.java:202)
> > >       at
> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManager.handleEvent(XmlRpcWorkflowManager.java:315)
> > >       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > >       at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> > >       at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> > >       at java.lang.reflect.Method.invoke(Unknown Source)
> > >       at org.apache.xmlrpc.Invoker.execute(Invoker.java:130)
> > >       at
> org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84)
> > >       at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146)
> > >       at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
> > >       at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125)
> > >       at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761)
> > >       at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642)
> > >       at java.lang.Thread.run(Unknown Source)
> > > org.apache.oodt.cas.workflow.structs.exceptions.EngineException: Unable
> to index workflow instance: [682adca4-c536-11e0-a906-354a8363ecc7]: Message:
> Lock obtain timed out: Lock@
> /tmp/lucene-76ae6fd29a43a2046fb462e76a907e1d-write.lock
> > >       at
> org.apache.oodt.cas.workflow.engine.ThreadPoolWorkflowEngine.persistWorkflowInstance(ThreadPoolWorkflowEngine.java:443)
> > >       at
> org.apache.oodt.cas.workflow.engine.ThreadPoolWorkflowEngine.startWorkflow(ThreadPoolWorkflowEngine.java:202)
> > >       at
> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManager.handleEvent(XmlRpcWorkflowManager.java:315)
> > >       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > >       at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> > >       at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> > >       at java.lang.reflect.Method.invoke(Unknown Source)
> > >       at org.apache.xmlrpc.Invoker.execute(Invoker.java:130)
> > >       at
> org.apache.xmlrpc.XmlRpcWorker.invokeHandler(XmlRpcWorker.java:84)
> > >       at org.apache.xmlrpc.XmlRpcWorker.execute(XmlRpcWorker.java:146)
> > >       at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:139)
> > >       at org.apache.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:125)
> > >       at org.apache.xmlrpc.WebServer$Connection.run(WebServer.java:761)
> > >       at org.apache.xmlrpc.WebServer$Runner.run(WebServer.java:642)
> > >       at java.lang.Thread.run(Unknown Source)
> > > Aug 12, 2011 3:57:09 PM sun.net.www.protocol.http.HttpURLConnection
> getInputStream
> > > FINE: sun.net.www.MessageHeader@122ce9085 pairs: {null: HTTP/1.1 200
> OK}{Server: Apache XML-RPC 1.0}{Connection: close}{Content-Type:
> text/xml}{Content-Length: 542}
> > > org.apache.xmlrpc.XmlRpcException: java.lang.Exception:
> org.apache.oodt.cas.workflow.structs.exceptions.EngineException: Engine
> exception when starting workflow: pythonWorkflow: Message: Unable to index
> workflow instance: [682adca4-c536-11e0-a906-354a8363ecc7]: Message: Lock
> obtain timed out: Lock@
> /tmp/lucene-76ae6fd29a43a2046fb462e76a907e1d-write.lock
> > >       at
> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeException(XmlRpcClientResponseProcessor.java:104)
> > >       at
> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcClientResponseProcessor.java:71)
> > >       at
> org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:73)
> > >       at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:194)
> > >       at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:185)
> > >       at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:178)
> > >       at
> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.sendEvent(XmlRpcWorkflowManagerClient.java:443)
> > >       at
> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main(XmlRpcWorkflowManagerClient.java:763)
> > > java.lang.Exception: java.lang.Exception:
> org.apache.oodt.cas.workflow.structs.exceptions.EngineException: Engine
> exception when starting workflow: pythonWorkflow: Message: Unable to index
> workflow instance: [682adca4-c536-11e0-a906-354a8363ecc7]: Message: Lock
> obtain timed out: Lock@
> /tmp/lucene-76ae6fd29a43a2046fb462e76a907e1d-write.lock
> > >
> > > I am not sure whats causing this and this is the first time I've seen
> this issue while working with the wmgr.
> > >
> > > Thanks,
> > > Sheryl
> >
> >
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > Chris Mattmann, Ph.D.
> > Senior Computer Scientist
> > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> > Office: 171-266B, Mailstop: 171-246
> > Email: chris.a.mattmann@nasa.gov
> > WWW:   http://sunset.usc.edu/~mattmann/
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > Adjunct Assistant Professor, Computer Science Department
> > University of Southern California, Los Angeles, CA 90089 USA
> > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >
> >
> >
> >
> > --
> > -Sheryl
>
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: chris.a.mattmann@nasa.gov
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>


-- 
-Sheryl

Mime
View raw message