Hey Sheryl,

We don't have a tool (other than downloading http://getopt.org/luke/ and 
deleting the record from the lucene workflow inst. repo) to remove entries 
from the workflow inst. repo. However, the way I usually just do it is blow 
away the inst. repo directory, restart WM and just go from there. 

Cheers,
Chris

On Oct 13, 2011, at 8:32 AM, Sheryl John wrote:

> Hi Chris,
> 
> Yes, I've never cleared an instance from the worker map. How I do clear it?
> Is there a command like the bash alias -'fmdel' that deletes a product from 
> the file manager catalog?
> 
> Thanks,
> 
> On Wed, Oct 12, 2011 at 8:04 PM, Mattmann, Chris A (388J) 
> <[email protected]> wrote:
> Hi Sheryl,
> 
> The issue you are seeing below happens when you try to stop an instance that 
> is already finished, but that
> is still in the worker map b/c you never restarted the WM and cleared it.
> 
> Cheers,
> Chris
> 
> On Oct 12, 2011, at 5:04 PM, Sheryl John wrote:
> 
> > Hi Rishi,
> >
> > Yes, you are using the command-line argument correctly. I just tried 
> > stopping some instances ( their statuses were FINISHED) and it works for me.
> >
> > I tried :
> > ./wmgr-client --url http://localhost:9001 --operation --stopWorkflowInst 
> > --id a2741f59-e631-11e0-ab26-03f35922ef75
> >
> >
> > The messages:
> >
> > WARNING: WorkflowEngine: Attempt to stop workflow instance id: 
> > a2741f59-e631-11e0-ab26-03f35922ef75, however, this engine is not tracking 
> > its execution
> > Oct 12, 2011 4:49:34 PM sun.net.www.protocol.http.HttpURLConnection 
> > getInputStream
> > FINE: sun.net.www.MessageHeader@6aa6aeed5 pairs: {null: HTTP/1.1 200 
> > OK}{Server: Apache XML-RPC 1.0}{Connection: close}{Content-Type: 
> > text/xml}{Content-Length: 121}
> > Successfully stopped workflow: [a2741f59-e631-11e0-ab26-03f35922ef75]
> >
> >
> > So, I'm not sure whats causing your NullPointerException.
> >
> > On Wed, Oct 12, 2011 at 4:41 PM, Verma, Rishi (388J) 
> > <[email protected]> wrote:
> > Hi all -
> >
> > I'm trying to stop one of my PGE workflows using the wmgr-client tool and 
> > the "--stopWorkflowinst" argument.
> >
> > I'm repeatedly getting a NullPointerException after trying to stop a 
> > running workflow.
> >
> > I believe I am using the '--stopWorkflowInst' argument correctly. Has 
> > anyone had luck with shutting down workflow PGE instances using this method?
> >
> > Thanks!
> > rishi
> >
> > -----
> > $ ./wmgr-client --url http://localhost:9001 --operation --getWorkflowInsts
> > ...
> > Instance: [id=ed798a3d-f075-11e0-bc2c-21311056edb2, status=CRAWLING, 
> > currentTask=urn:oodt:ProteomeLinux, 
> > workflow=ProteomeLinuxWorkflow,wallClockTime=8524.3347,currentTaskWallClockTime=3.2414]
> > ...
> >
> > $ ./wmgr-client --url http://localhost:9001 --operation --stopWorkflowInst 
> > --id ed798a3d-f075-11e0-bc2c-21311056edb2
> > org.apache.xmlrpc.XmlRpcException: java.lang.Exception: 
> > java.lang.NullPointerException
> >        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.stopWorkflowInstance(XmlRpcWorkflowManagerClient.java:341)
> >        at 
> > org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main(XmlRpcWorkflowManagerClient.java:907)
> > Exception in thread "main" java.lang.RuntimeException: java.lang.Exception: 
> > java.lang.NullPointerException
> >        at 
> > org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main(XmlRpcWorkflowManagerClient.java:913)
> >
> >
> >
> >
> > --
> > -Sheryl
> 
> 
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: [email protected]
> 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: [email protected]
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Reply via email to