You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@oodt.apache.org by "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov> on 2011/10/13 01:41:49 UTC

Shutting down CAS PGE workflow instances

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)

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

Hi Rishi,

I'm wondering if this has to do with trying to stop an instance that was no longer being 
managed by the Workflow Manager. The WM has a map that contains an id->Worker 
table of the current instances that are processing. Stopping an instance only works if 
the worker map contains the ID of the workflow instance that you are trying to stop.

Often the behavior below happens if e.g., you restarted the WM a few times after 
having some stuck workflows and then are trying to clear out those old records 
in your processing list by calling stopInst, yet the WM barks at you b/c it doesn't know 
anything about that ID anymore.

I've often thought that a way around this would be to *also* check the instance repository, 
for an instance that is still running (according to its last recorded persistence) and if so, 
grab it, instantiate a dummy object, mark it as "done", and then re-persist the instance 
as stopped.

A JIRA issue + a patch that implements that strategy would be most welcome (by anyone 
on this thread ^_^ or list ^_^).

Cheers,
Chris

On Oct 12, 2011, at 4:41 PM, Verma, Rishi (388J) 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)
> 


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

Hi Rishi,

I'm wondering if this has to do with trying to stop an instance that was no longer being 
managed by the Workflow Manager. The WM has a map that contains an id->Worker 
table of the current instances that are processing. Stopping an instance only works if 
the worker map contains the ID of the workflow instance that you are trying to stop.

Often the behavior below happens if e.g., you restarted the WM a few times after 
having some stuck workflows and then are trying to clear out those old records 
in your processing list by calling stopInst, yet the WM barks at you b/c it doesn't know 
anything about that ID anymore.

I've often thought that a way around this would be to *also* check the instance repository, 
for an instance that is still running (according to its last recorded persistence) and if so, 
grab it, instantiate a dummy object, mark it as "done", and then re-persist the instance 
as stopped.

A JIRA issue + a patch that implements that strategy would be most welcome (by anyone 
on this thread ^_^ or list ^_^).

Cheers,
Chris

On Oct 12, 2011, at 4:41 PM, Verma, Rishi (388J) 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)
> 


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

Yep, right now the build is broke since I'm working on OODT-310.

I'll try my best to wrap it up soon. I could disable workflow in the build, 
but then I'd have to disable a bunch of dependent modules and it would 
be a mess.

Cheers,
Chris

On Oct 12, 2011, at 5:38 PM, Sheryl John wrote:

> I faced similar issues with the latest build while working OODT-323.
> Chris informed me that he was working some issues and hence the exceptions with the latest build.
> 
> On Wed, Oct 12, 2011 at 5:32 PM, Verma, Rishi (388J) <Ri...@jpl.nasa.gov> wrote:
> Hi Shreyl,
> 
> Thanks for the confirmation!
> 
> I am using 0.4-SNAPSHOT.
> 
> I just checked and 0.3-SNAPSHOT is able to stop workflows via WorkflowInst ID just fine.
> 
> Something new in the latest build must have broke.. will look into it and file an issue if I find some problem in the code.
> 
> thanks -
> rishi
> 
> On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:
> 
>> Which version of the Workflow Manager are you working on?
>> 
>> Try the 0.3-SNAPSHOT version if you working on one of the latest versions of the trunk. I'm not sure if this will fix this.
>> 
>> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com> 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) <Ri...@jpl.nasa.gov> 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
>> 
>> 
>> 
>> -- 
>> -Sheryl
> 
> 
> 
> 
> -- 
> -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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

Yep, right now the build is broke since I'm working on OODT-310.

I'll try my best to wrap it up soon. I could disable workflow in the build, 
but then I'd have to disable a bunch of dependent modules and it would 
be a mess.

Cheers,
Chris

On Oct 12, 2011, at 5:38 PM, Sheryl John wrote:

> I faced similar issues with the latest build while working OODT-323.
> Chris informed me that he was working some issues and hence the exceptions with the latest build.
> 
> On Wed, Oct 12, 2011 at 5:32 PM, Verma, Rishi (388J) <Ri...@jpl.nasa.gov> wrote:
> Hi Shreyl,
> 
> Thanks for the confirmation!
> 
> I am using 0.4-SNAPSHOT.
> 
> I just checked and 0.3-SNAPSHOT is able to stop workflows via WorkflowInst ID just fine.
> 
> Something new in the latest build must have broke.. will look into it and file an issue if I find some problem in the code.
> 
> thanks -
> rishi
> 
> On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:
> 
>> Which version of the Workflow Manager are you working on?
>> 
>> Try the 0.3-SNAPSHOT version if you working on one of the latest versions of the trunk. I'm not sure if this will fix this.
>> 
>> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com> 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) <Ri...@jpl.nasa.gov> 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
>> 
>> 
>> 
>> -- 
>> -Sheryl
> 
> 
> 
> 
> -- 
> -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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by Sheryl John <sh...@gmail.com>.

I faced similar issues with the latest build while working OODT-323.
Chris informed me that he was working some issues and hence the exceptions
with the latest build.

On Wed, Oct 12, 2011 at 5:32 PM, Verma, Rishi (388J) <
Rishi.Verma@jpl.nasa.gov> wrote:

> Hi Shreyl,
>
> Thanks for the confirmation!
>
> I am using 0.4-SNAPSHOT.
>
> I just checked and 0.3-SNAPSHOT is able to stop workflows via WorkflowInst
> ID just fine.
>
> Something new in the latest build must have broke.. will look into it and
> file an issue if I find some problem in the code.
>
> thanks -
> rishi
>
> On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:
>
> Which version of the Workflow Manager are you working on?
>
> Try the 0.3-SNAPSHOT version if you working on one of the latest versions
> of the trunk. I'm not sure if this will fix this.
>
> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com> 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) <
>> Rishi.Verma@jpl.nasa.gov> 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
>>
>
>
>
> --
> -Sheryl
>
>
>


-- 
-Sheryl

Re: Shutting down CAS PGE workflow instances

Posted by Sheryl John <sh...@gmail.com>.

I faced similar issues with the latest build while working OODT-323.
Chris informed me that he was working some issues and hence the exceptions
with the latest build.

On Wed, Oct 12, 2011 at 5:32 PM, Verma, Rishi (388J) <
Rishi.Verma@jpl.nasa.gov> wrote:

> Hi Shreyl,
>
> Thanks for the confirmation!
>
> I am using 0.4-SNAPSHOT.
>
> I just checked and 0.3-SNAPSHOT is able to stop workflows via WorkflowInst
> ID just fine.
>
> Something new in the latest build must have broke.. will look into it and
> file an issue if I find some problem in the code.
>
> thanks -
> rishi
>
> On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:
>
> Which version of the Workflow Manager are you working on?
>
> Try the 0.3-SNAPSHOT version if you working on one of the latest versions
> of the trunk. I'm not sure if this will fix this.
>
> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com> 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) <
>> Rishi.Verma@jpl.nasa.gov> 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
>>
>
>
>
> --
> -Sheryl
>
>
>


-- 
-Sheryl

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

Great, thanks Mike!

On Oct 18, 2011, at 2:14 PM, Cayanan, Michael D (388J) wrote:

> Hi Chris,
> 
> Nope. Just wondering since SMAP will be using version 0.3. Wanted to make
> sure that this wasn't a workflow 0.3 issue.
> 
> Thanks,
> Mike
> 
> On 10/17/11 8:02 PM, "Mattmann, Chris A (388J)"
> <ch...@jpl.nasa.gov> wrote:
> 
>> Hi Mike,
>> 
>> Yep as far as I know. Do you have something specific you're seeing?
>> 
>> Cheers,
>> Chris
>> 
>> On Oct 17, 2011, at 4:07 PM, Cayanan, Michael D (388J) wrote:
>> 
>>> Thanks for the info Rishi and Chris.
>>> 
>>> So from what this sounds like, the issue here is that the worker map
>>> wasn't cleared. So whether you're using 0.3 or 0.4, it doesn't matter in
>>> this case?
>>> 
>>> -Mike
>>> 
>>> On 10/14/11 8:29 PM, "Mattmann, Chris A (388J)"
>>> <ch...@jpl.nasa.gov> wrote:
>>> 
>>>> Hi Mike,
>>>> 
>>>> FYI, see my mail to Sheryl the other day:
>>>> 
>>>> http://markmail.org/message/wejycqx5tzs5qwoj
>>>> 
>>>> Cheers,
>>>> Chris
>>>> 
>>>> 
>>>> On Oct 14, 2011, at 8:42 AM, Cayanan, Michael D (388J) wrote:
>>>> 
>>>>> Hi Rishi,
>>>>> 
>>>>> Do you know if using version 0.3 (the official released version) will
>>>>> resolve this issue as well?
>>>>> 
>>>>> Thanks,
>>>>> Mike 
>>>>> 
>>>>> From: "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>
>>>>> Reply-To: "user@oodt.apache.org" <us...@oodt.apache.org>
>>>>> Date: Wed, 12 Oct 2011 17:32:09 -0700
>>>>> To: "user@oodt.apache.org" <us...@oodt.apache.org>
>>>>> Subject: Re: Shutting down CAS PGE workflow instances
>>>>> 
>>>>> Hi Shreyl,
>>>>> 
>>>>> Thanks for the confirmation!
>>>>> 
>>>>> I am using 0.4-SNAPSHOT.
>>>>> 
>>>>> I just checked and 0.3-SNAPSHOT is able to stop workflows via
>>>>> WorkflowInst ID just fine.
>>>>> 
>>>>> Something new in the latest build must have broke.. will look into it
>>>>> and file an issue if I find some problem in the code.
>>>>> 
>>>>> thanks -
>>>>> rishi
>>>>> 
>>>>> On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:
>>>>> 
>>>>>> Which version of the Workflow Manager are you working on?
>>>>>> 
>>>>>> Try the 0.3-SNAPSHOT version if you working on one of the latest
>>>>>> versions of the trunk. I'm not sure if this will fix this.
>>>>>> 
>>>>>> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com>
>>>>>> 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)
>>>>>>> <Ri...@jpl.nasa.gov> 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,currentTaskWa
>>>>>>>> ll
>>>>>>>> ClockTime=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(XmlR
>>>>>>>> pc
>>>>>>>> ClientResponseProcessor.java:104)
>>>>>>>>      at 
>>>>>>>> 
>>>>>>>> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRp
>>>>>>>> cC
>>>>>>>> lientResponseProcessor.java:71)
>>>>>>>>      at 
>>>>>>>> 
>>>>>>>> org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java
>>>>>>>> :7
>>>>>>>> 3)
>>>>>>>>      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.stop
>>>>>>>> Wo
>>>>>>>> rkflowInstance(XmlRpcWorkflowManagerClient.java:341)
>>>>>>>>      at 
>>>>>>>> 
>>>>>>>> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main
>>>>>>>> (X
>>>>>>>> mlRpcWorkflowManagerClient.java:907)
>>>>>>>> Exception in thread "main" java.lang.RuntimeException:
>>>>>>>> java.lang.Exception: java.lang.NullPointerException
>>>>>>>>      at 
>>>>>>>> 
>>>>>>>> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main
>>>>>>>> (X
>>>>>>>> mlRpcWorkflowManagerClient.java:913)
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> -- 
>>>>>>> -Sheryl
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> -- 
>>>>>> -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
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 
>>> 
>> 
>> 
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
> 


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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/
Phone: +1 (818) 354-8810
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

Great, thanks Mike!

On Oct 18, 2011, at 2:14 PM, Cayanan, Michael D (388J) wrote:

> Hi Chris,
> 
> Nope. Just wondering since SMAP will be using version 0.3. Wanted to make
> sure that this wasn't a workflow 0.3 issue.
> 
> Thanks,
> Mike
> 
> On 10/17/11 8:02 PM, "Mattmann, Chris A (388J)"
> <ch...@jpl.nasa.gov> wrote:
> 
>> Hi Mike,
>> 
>> Yep as far as I know. Do you have something specific you're seeing?
>> 
>> Cheers,
>> Chris
>> 
>> On Oct 17, 2011, at 4:07 PM, Cayanan, Michael D (388J) wrote:
>> 
>>> Thanks for the info Rishi and Chris.
>>> 
>>> So from what this sounds like, the issue here is that the worker map
>>> wasn't cleared. So whether you're using 0.3 or 0.4, it doesn't matter in
>>> this case?
>>> 
>>> -Mike
>>> 
>>> On 10/14/11 8:29 PM, "Mattmann, Chris A (388J)"
>>> <ch...@jpl.nasa.gov> wrote:
>>> 
>>>> Hi Mike,
>>>> 
>>>> FYI, see my mail to Sheryl the other day:
>>>> 
>>>> http://markmail.org/message/wejycqx5tzs5qwoj
>>>> 
>>>> Cheers,
>>>> Chris
>>>> 
>>>> 
>>>> On Oct 14, 2011, at 8:42 AM, Cayanan, Michael D (388J) wrote:
>>>> 
>>>>> Hi Rishi,
>>>>> 
>>>>> Do you know if using version 0.3 (the official released version) will
>>>>> resolve this issue as well?
>>>>> 
>>>>> Thanks,
>>>>> Mike 
>>>>> 
>>>>> From: "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>
>>>>> Reply-To: "user@oodt.apache.org" <us...@oodt.apache.org>
>>>>> Date: Wed, 12 Oct 2011 17:32:09 -0700
>>>>> To: "user@oodt.apache.org" <us...@oodt.apache.org>
>>>>> Subject: Re: Shutting down CAS PGE workflow instances
>>>>> 
>>>>> Hi Shreyl,
>>>>> 
>>>>> Thanks for the confirmation!
>>>>> 
>>>>> I am using 0.4-SNAPSHOT.
>>>>> 
>>>>> I just checked and 0.3-SNAPSHOT is able to stop workflows via
>>>>> WorkflowInst ID just fine.
>>>>> 
>>>>> Something new in the latest build must have broke.. will look into it
>>>>> and file an issue if I find some problem in the code.
>>>>> 
>>>>> thanks -
>>>>> rishi
>>>>> 
>>>>> On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:
>>>>> 
>>>>>> Which version of the Workflow Manager are you working on?
>>>>>> 
>>>>>> Try the 0.3-SNAPSHOT version if you working on one of the latest
>>>>>> versions of the trunk. I'm not sure if this will fix this.
>>>>>> 
>>>>>> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com>
>>>>>> 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)
>>>>>>> <Ri...@jpl.nasa.gov> 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,currentTaskWa
>>>>>>>> ll
>>>>>>>> ClockTime=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(XmlR
>>>>>>>> pc
>>>>>>>> ClientResponseProcessor.java:104)
>>>>>>>>      at 
>>>>>>>> 
>>>>>>>> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRp
>>>>>>>> cC
>>>>>>>> lientResponseProcessor.java:71)
>>>>>>>>      at 
>>>>>>>> 
>>>>>>>> org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java
>>>>>>>> :7
>>>>>>>> 3)
>>>>>>>>      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.stop
>>>>>>>> Wo
>>>>>>>> rkflowInstance(XmlRpcWorkflowManagerClient.java:341)
>>>>>>>>      at 
>>>>>>>> 
>>>>>>>> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main
>>>>>>>> (X
>>>>>>>> mlRpcWorkflowManagerClient.java:907)
>>>>>>>> Exception in thread "main" java.lang.RuntimeException:
>>>>>>>> java.lang.Exception: java.lang.NullPointerException
>>>>>>>>      at 
>>>>>>>> 
>>>>>>>> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main
>>>>>>>> (X
>>>>>>>> mlRpcWorkflowManagerClient.java:913)
>>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> -- 
>>>>>>> -Sheryl
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> -- 
>>>>>> -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
>>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>>> 
>>> 
>> 
>> 
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
> 


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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/
Phone: +1 (818) 354-8810
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by "Cayanan, Michael D (388J)" <mi...@jpl.nasa.gov>.

Hi Chris,

Nope. Just wondering since SMAP will be using version 0.3. Wanted to make
sure that this wasn't a workflow 0.3 issue.

Thanks,
Mike

On 10/17/11 8:02 PM, "Mattmann, Chris A (388J)"
<ch...@jpl.nasa.gov> wrote:

>Hi Mike,
>
>Yep as far as I know. Do you have something specific you're seeing?
>
>Cheers,
>Chris
>
>On Oct 17, 2011, at 4:07 PM, Cayanan, Michael D (388J) wrote:
>
>> Thanks for the info Rishi and Chris.
>> 
>> So from what this sounds like, the issue here is that the worker map
>> wasn't cleared. So whether you're using 0.3 or 0.4, it doesn't matter in
>> this case?
>> 
>> -Mike
>> 
>> On 10/14/11 8:29 PM, "Mattmann, Chris A (388J)"
>> <ch...@jpl.nasa.gov> wrote:
>> 
>>> Hi Mike,
>>> 
>>> FYI, see my mail to Sheryl the other day:
>>> 
>>> http://markmail.org/message/wejycqx5tzs5qwoj
>>> 
>>> Cheers,
>>> Chris
>>> 
>>> 
>>> On Oct 14, 2011, at 8:42 AM, Cayanan, Michael D (388J) wrote:
>>> 
>>>> Hi Rishi,
>>>> 
>>>> Do you know if using version 0.3 (the official released version) will
>>>> resolve this issue as well?
>>>> 
>>>> Thanks,
>>>> Mike 
>>>> 
>>>> From: "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>
>>>> Reply-To: "user@oodt.apache.org" <us...@oodt.apache.org>
>>>> Date: Wed, 12 Oct 2011 17:32:09 -0700
>>>> To: "user@oodt.apache.org" <us...@oodt.apache.org>
>>>> Subject: Re: Shutting down CAS PGE workflow instances
>>>> 
>>>> Hi Shreyl,
>>>> 
>>>> Thanks for the confirmation!
>>>> 
>>>> I am using 0.4-SNAPSHOT.
>>>> 
>>>> I just checked and 0.3-SNAPSHOT is able to stop workflows via
>>>> WorkflowInst ID just fine.
>>>> 
>>>> Something new in the latest build must have broke.. will look into it
>>>> and file an issue if I find some problem in the code.
>>>> 
>>>> thanks -
>>>> rishi
>>>> 
>>>> On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:
>>>> 
>>>>> Which version of the Workflow Manager are you working on?
>>>>> 
>>>>> Try the 0.3-SNAPSHOT version if you working on one of the latest
>>>>> versions of the trunk. I'm not sure if this will fix this.
>>>>> 
>>>>> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com>
>>>>> 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)
>>>>>> <Ri...@jpl.nasa.gov> 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,currentTaskWa
>>>>>>>ll
>>>>>>> ClockTime=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(XmlR
>>>>>>>pc
>>>>>>> ClientResponseProcessor.java:104)
>>>>>>>       at 
>>>>>>> 
>>>>>>>org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRp
>>>>>>>cC
>>>>>>> lientResponseProcessor.java:71)
>>>>>>>       at 
>>>>>>> 
>>>>>>>org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java
>>>>>>>:7
>>>>>>> 3)
>>>>>>>       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.stop
>>>>>>>Wo
>>>>>>> rkflowInstance(XmlRpcWorkflowManagerClient.java:341)
>>>>>>>       at 
>>>>>>> 
>>>>>>>org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main
>>>>>>>(X
>>>>>>> mlRpcWorkflowManagerClient.java:907)
>>>>>>> Exception in thread "main" java.lang.RuntimeException:
>>>>>>> java.lang.Exception: java.lang.NullPointerException
>>>>>>>       at 
>>>>>>> 
>>>>>>>org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main
>>>>>>>(X
>>>>>>> mlRpcWorkflowManagerClient.java:913)
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> -- 
>>>>>> -Sheryl
>>>>> 
>>>>> 
>>>>> 
>>>>> -- 
>>>>> -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
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> 
>> 
>
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>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
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>

Re: Shutting down CAS PGE workflow instances

Posted by "Cayanan, Michael D (388J)" <mi...@jpl.nasa.gov>.

Hi Chris,

Nope. Just wondering since SMAP will be using version 0.3. Wanted to make
sure that this wasn't a workflow 0.3 issue.

Thanks,
Mike

On 10/17/11 8:02 PM, "Mattmann, Chris A (388J)"
<ch...@jpl.nasa.gov> wrote:

>Hi Mike,
>
>Yep as far as I know. Do you have something specific you're seeing?
>
>Cheers,
>Chris
>
>On Oct 17, 2011, at 4:07 PM, Cayanan, Michael D (388J) wrote:
>
>> Thanks for the info Rishi and Chris.
>> 
>> So from what this sounds like, the issue here is that the worker map
>> wasn't cleared. So whether you're using 0.3 or 0.4, it doesn't matter in
>> this case?
>> 
>> -Mike
>> 
>> On 10/14/11 8:29 PM, "Mattmann, Chris A (388J)"
>> <ch...@jpl.nasa.gov> wrote:
>> 
>>> Hi Mike,
>>> 
>>> FYI, see my mail to Sheryl the other day:
>>> 
>>> http://markmail.org/message/wejycqx5tzs5qwoj
>>> 
>>> Cheers,
>>> Chris
>>> 
>>> 
>>> On Oct 14, 2011, at 8:42 AM, Cayanan, Michael D (388J) wrote:
>>> 
>>>> Hi Rishi,
>>>> 
>>>> Do you know if using version 0.3 (the official released version) will
>>>> resolve this issue as well?
>>>> 
>>>> Thanks,
>>>> Mike 
>>>> 
>>>> From: "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>
>>>> Reply-To: "user@oodt.apache.org" <us...@oodt.apache.org>
>>>> Date: Wed, 12 Oct 2011 17:32:09 -0700
>>>> To: "user@oodt.apache.org" <us...@oodt.apache.org>
>>>> Subject: Re: Shutting down CAS PGE workflow instances
>>>> 
>>>> Hi Shreyl,
>>>> 
>>>> Thanks for the confirmation!
>>>> 
>>>> I am using 0.4-SNAPSHOT.
>>>> 
>>>> I just checked and 0.3-SNAPSHOT is able to stop workflows via
>>>> WorkflowInst ID just fine.
>>>> 
>>>> Something new in the latest build must have broke.. will look into it
>>>> and file an issue if I find some problem in the code.
>>>> 
>>>> thanks -
>>>> rishi
>>>> 
>>>> On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:
>>>> 
>>>>> Which version of the Workflow Manager are you working on?
>>>>> 
>>>>> Try the 0.3-SNAPSHOT version if you working on one of the latest
>>>>> versions of the trunk. I'm not sure if this will fix this.
>>>>> 
>>>>> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com>
>>>>> 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)
>>>>>> <Ri...@jpl.nasa.gov> 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,currentTaskWa
>>>>>>>ll
>>>>>>> ClockTime=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(XmlR
>>>>>>>pc
>>>>>>> ClientResponseProcessor.java:104)
>>>>>>>       at 
>>>>>>> 
>>>>>>>org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRp
>>>>>>>cC
>>>>>>> lientResponseProcessor.java:71)
>>>>>>>       at 
>>>>>>> 
>>>>>>>org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java
>>>>>>>:7
>>>>>>> 3)
>>>>>>>       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.stop
>>>>>>>Wo
>>>>>>> rkflowInstance(XmlRpcWorkflowManagerClient.java:341)
>>>>>>>       at 
>>>>>>> 
>>>>>>>org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main
>>>>>>>(X
>>>>>>> mlRpcWorkflowManagerClient.java:907)
>>>>>>> Exception in thread "main" java.lang.RuntimeException:
>>>>>>> java.lang.Exception: java.lang.NullPointerException
>>>>>>>       at 
>>>>>>> 
>>>>>>>org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main
>>>>>>>(X
>>>>>>> mlRpcWorkflowManagerClient.java:913)
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> -- 
>>>>>> -Sheryl
>>>>> 
>>>>> 
>>>>> 
>>>>> -- 
>>>>> -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
>>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>>> 
>> 
>
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>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
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

Hi Mike,

Yep as far as I know. Do you have something specific you're seeing?

Cheers,
Chris

On Oct 17, 2011, at 4:07 PM, Cayanan, Michael D (388J) wrote:

> Thanks for the info Rishi and Chris.
> 
> So from what this sounds like, the issue here is that the worker map
> wasn't cleared. So whether you're using 0.3 or 0.4, it doesn't matter in
> this case?
> 
> -Mike
> 
> On 10/14/11 8:29 PM, "Mattmann, Chris A (388J)"
> <ch...@jpl.nasa.gov> wrote:
> 
>> Hi Mike,
>> 
>> FYI, see my mail to Sheryl the other day:
>> 
>> http://markmail.org/message/wejycqx5tzs5qwoj
>> 
>> Cheers,
>> Chris
>> 
>> 
>> On Oct 14, 2011, at 8:42 AM, Cayanan, Michael D (388J) wrote:
>> 
>>> Hi Rishi,
>>> 
>>> Do you know if using version 0.3 (the official released version) will
>>> resolve this issue as well?
>>> 
>>> Thanks,
>>> Mike 
>>> 
>>> From: "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>
>>> Reply-To: "user@oodt.apache.org" <us...@oodt.apache.org>
>>> Date: Wed, 12 Oct 2011 17:32:09 -0700
>>> To: "user@oodt.apache.org" <us...@oodt.apache.org>
>>> Subject: Re: Shutting down CAS PGE workflow instances
>>> 
>>> Hi Shreyl,
>>> 
>>> Thanks for the confirmation!
>>> 
>>> I am using 0.4-SNAPSHOT.
>>> 
>>> I just checked and 0.3-SNAPSHOT is able to stop workflows via
>>> WorkflowInst ID just fine.
>>> 
>>> Something new in the latest build must have broke.. will look into it
>>> and file an issue if I find some problem in the code.
>>> 
>>> thanks -
>>> rishi
>>> 
>>> On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:
>>> 
>>>> Which version of the Workflow Manager are you working on?
>>>> 
>>>> Try the 0.3-SNAPSHOT version if you working on one of the latest
>>>> versions of the trunk. I'm not sure if this will fix this.
>>>> 
>>>> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com>
>>>> 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)
>>>>> <Ri...@jpl.nasa.gov> 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,currentTaskWall
>>>>>> ClockTime=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(XmlRpc
>>>>>> ClientResponseProcessor.java:104)
>>>>>>       at 
>>>>>> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcC
>>>>>> lientResponseProcessor.java:71)
>>>>>>       at 
>>>>>> org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:7
>>>>>> 3)
>>>>>>       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.stopWo
>>>>>> rkflowInstance(XmlRpcWorkflowManagerClient.java:341)
>>>>>>       at 
>>>>>> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main(X
>>>>>> mlRpcWorkflowManagerClient.java:907)
>>>>>> Exception in thread "main" java.lang.RuntimeException:
>>>>>> java.lang.Exception: java.lang.NullPointerException
>>>>>>       at 
>>>>>> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main(X
>>>>>> mlRpcWorkflowManagerClient.java:913)
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> -- 
>>>>> -Sheryl
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> -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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
> 


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

Hi Mike,

Yep as far as I know. Do you have something specific you're seeing?

Cheers,
Chris

On Oct 17, 2011, at 4:07 PM, Cayanan, Michael D (388J) wrote:

> Thanks for the info Rishi and Chris.
> 
> So from what this sounds like, the issue here is that the worker map
> wasn't cleared. So whether you're using 0.3 or 0.4, it doesn't matter in
> this case?
> 
> -Mike
> 
> On 10/14/11 8:29 PM, "Mattmann, Chris A (388J)"
> <ch...@jpl.nasa.gov> wrote:
> 
>> Hi Mike,
>> 
>> FYI, see my mail to Sheryl the other day:
>> 
>> http://markmail.org/message/wejycqx5tzs5qwoj
>> 
>> Cheers,
>> Chris
>> 
>> 
>> On Oct 14, 2011, at 8:42 AM, Cayanan, Michael D (388J) wrote:
>> 
>>> Hi Rishi,
>>> 
>>> Do you know if using version 0.3 (the official released version) will
>>> resolve this issue as well?
>>> 
>>> Thanks,
>>> Mike 
>>> 
>>> From: "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>
>>> Reply-To: "user@oodt.apache.org" <us...@oodt.apache.org>
>>> Date: Wed, 12 Oct 2011 17:32:09 -0700
>>> To: "user@oodt.apache.org" <us...@oodt.apache.org>
>>> Subject: Re: Shutting down CAS PGE workflow instances
>>> 
>>> Hi Shreyl,
>>> 
>>> Thanks for the confirmation!
>>> 
>>> I am using 0.4-SNAPSHOT.
>>> 
>>> I just checked and 0.3-SNAPSHOT is able to stop workflows via
>>> WorkflowInst ID just fine.
>>> 
>>> Something new in the latest build must have broke.. will look into it
>>> and file an issue if I find some problem in the code.
>>> 
>>> thanks -
>>> rishi
>>> 
>>> On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:
>>> 
>>>> Which version of the Workflow Manager are you working on?
>>>> 
>>>> Try the 0.3-SNAPSHOT version if you working on one of the latest
>>>> versions of the trunk. I'm not sure if this will fix this.
>>>> 
>>>> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com>
>>>> 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)
>>>>> <Ri...@jpl.nasa.gov> 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,currentTaskWall
>>>>>> ClockTime=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(XmlRpc
>>>>>> ClientResponseProcessor.java:104)
>>>>>>       at 
>>>>>> org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcC
>>>>>> lientResponseProcessor.java:71)
>>>>>>       at 
>>>>>> org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:7
>>>>>> 3)
>>>>>>       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.stopWo
>>>>>> rkflowInstance(XmlRpcWorkflowManagerClient.java:341)
>>>>>>       at 
>>>>>> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main(X
>>>>>> mlRpcWorkflowManagerClient.java:907)
>>>>>> Exception in thread "main" java.lang.RuntimeException:
>>>>>> java.lang.Exception: java.lang.NullPointerException
>>>>>>       at 
>>>>>> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main(X
>>>>>> mlRpcWorkflowManagerClient.java:913)
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> -- 
>>>>> -Sheryl
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> -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
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 
> 


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by "Cayanan, Michael D (388J)" <mi...@jpl.nasa.gov>.

Thanks for the info Rishi and Chris.

So from what this sounds like, the issue here is that the worker map
wasn't cleared. So whether you're using 0.3 or 0.4, it doesn't matter in
this case?

-Mike

On 10/14/11 8:29 PM, "Mattmann, Chris A (388J)"
<ch...@jpl.nasa.gov> wrote:

>Hi Mike,
>
>FYI, see my mail to Sheryl the other day:
>
>http://markmail.org/message/wejycqx5tzs5qwoj
>
>Cheers,
>Chris
>
>
>On Oct 14, 2011, at 8:42 AM, Cayanan, Michael D (388J) wrote:
>
>> Hi Rishi,
>> 
>> Do you know if using version 0.3 (the official released version) will
>>resolve this issue as well?
>> 
>> Thanks,
>> Mike 
>> 
>> From: "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>
>> Reply-To: "user@oodt.apache.org" <us...@oodt.apache.org>
>> Date: Wed, 12 Oct 2011 17:32:09 -0700
>> To: "user@oodt.apache.org" <us...@oodt.apache.org>
>> Subject: Re: Shutting down CAS PGE workflow instances
>> 
>> Hi Shreyl,
>> 
>> Thanks for the confirmation!
>> 
>> I am using 0.4-SNAPSHOT.
>> 
>> I just checked and 0.3-SNAPSHOT is able to stop workflows via
>>WorkflowInst ID just fine.
>> 
>> Something new in the latest build must have broke.. will look into it
>>and file an issue if I find some problem in the code.
>> 
>> thanks -
>> rishi
>> 
>> On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:
>> 
>>> Which version of the Workflow Manager are you working on?
>>> 
>>> Try the 0.3-SNAPSHOT version if you working on one of the latest
>>>versions of the trunk. I'm not sure if this will fix this.
>>> 
>>> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com>
>>>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)
>>>><Ri...@jpl.nasa.gov> 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,currentTaskWall
>>>>>ClockTime=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(XmlRpc
>>>>>ClientResponseProcessor.java:104)
>>>>>        at 
>>>>>org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcC
>>>>>lientResponseProcessor.java:71)
>>>>>        at 
>>>>>org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:7
>>>>>3)
>>>>>        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.stopWo
>>>>>rkflowInstance(XmlRpcWorkflowManagerClient.java:341)
>>>>>        at 
>>>>>org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main(X
>>>>>mlRpcWorkflowManagerClient.java:907)
>>>>> Exception in thread "main" java.lang.RuntimeException:
>>>>>java.lang.Exception: java.lang.NullPointerException
>>>>>        at 
>>>>>org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main(X
>>>>>mlRpcWorkflowManagerClient.java:913)
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> -Sheryl
>>> 
>>> 
>>> 
>>> -- 
>>> -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
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>

Re: Shutting down CAS PGE workflow instances

Posted by "Cayanan, Michael D (388J)" <mi...@jpl.nasa.gov>.

Thanks for the info Rishi and Chris.

So from what this sounds like, the issue here is that the worker map
wasn't cleared. So whether you're using 0.3 or 0.4, it doesn't matter in
this case?

-Mike

On 10/14/11 8:29 PM, "Mattmann, Chris A (388J)"
<ch...@jpl.nasa.gov> wrote:

>Hi Mike,
>
>FYI, see my mail to Sheryl the other day:
>
>http://markmail.org/message/wejycqx5tzs5qwoj
>
>Cheers,
>Chris
>
>
>On Oct 14, 2011, at 8:42 AM, Cayanan, Michael D (388J) wrote:
>
>> Hi Rishi,
>> 
>> Do you know if using version 0.3 (the official released version) will
>>resolve this issue as well?
>> 
>> Thanks,
>> Mike 
>> 
>> From: "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>
>> Reply-To: "user@oodt.apache.org" <us...@oodt.apache.org>
>> Date: Wed, 12 Oct 2011 17:32:09 -0700
>> To: "user@oodt.apache.org" <us...@oodt.apache.org>
>> Subject: Re: Shutting down CAS PGE workflow instances
>> 
>> Hi Shreyl,
>> 
>> Thanks for the confirmation!
>> 
>> I am using 0.4-SNAPSHOT.
>> 
>> I just checked and 0.3-SNAPSHOT is able to stop workflows via
>>WorkflowInst ID just fine.
>> 
>> Something new in the latest build must have broke.. will look into it
>>and file an issue if I find some problem in the code.
>> 
>> thanks -
>> rishi
>> 
>> On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:
>> 
>>> Which version of the Workflow Manager are you working on?
>>> 
>>> Try the 0.3-SNAPSHOT version if you working on one of the latest
>>>versions of the trunk. I'm not sure if this will fix this.
>>> 
>>> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com>
>>>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)
>>>><Ri...@jpl.nasa.gov> 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,currentTaskWall
>>>>>ClockTime=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(XmlRpc
>>>>>ClientResponseProcessor.java:104)
>>>>>        at 
>>>>>org.apache.xmlrpc.XmlRpcClientResponseProcessor.decodeResponse(XmlRpcC
>>>>>lientResponseProcessor.java:71)
>>>>>        at 
>>>>>org.apache.xmlrpc.XmlRpcClientWorker.execute(XmlRpcClientWorker.java:7
>>>>>3)
>>>>>        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.stopWo
>>>>>rkflowInstance(XmlRpcWorkflowManagerClient.java:341)
>>>>>        at 
>>>>>org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main(X
>>>>>mlRpcWorkflowManagerClient.java:907)
>>>>> Exception in thread "main" java.lang.RuntimeException:
>>>>>java.lang.Exception: java.lang.NullPointerException
>>>>>        at 
>>>>>org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main(X
>>>>>mlRpcWorkflowManagerClient.java:913)
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> -Sheryl
>>> 
>>> 
>>> 
>>> -- 
>>> -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
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

Hi Mike,

FYI, see my mail to Sheryl the other day:

http://markmail.org/message/wejycqx5tzs5qwoj

Cheers,
Chris


On Oct 14, 2011, at 8:42 AM, Cayanan, Michael D (388J) wrote:

> Hi Rishi,
> 
> Do you know if using version 0.3 (the official released version) will resolve this issue as well?
> 
> Thanks,
> Mike 
> 
> From: "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>
> Reply-To: "user@oodt.apache.org" <us...@oodt.apache.org>
> Date: Wed, 12 Oct 2011 17:32:09 -0700
> To: "user@oodt.apache.org" <us...@oodt.apache.org>
> Subject: Re: Shutting down CAS PGE workflow instances
> 
> Hi Shreyl,
> 
> Thanks for the confirmation!
> 
> I am using 0.4-SNAPSHOT.
> 
> I just checked and 0.3-SNAPSHOT is able to stop workflows via WorkflowInst ID just fine.
> 
> Something new in the latest build must have broke.. will look into it and file an issue if I find some problem in the code.
> 
> thanks -
> rishi
> 
> On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:
> 
>> Which version of the Workflow Manager are you working on?
>> 
>> Try the 0.3-SNAPSHOT version if you working on one of the latest versions of the trunk. I'm not sure if this will fix this.
>> 
>> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com> 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) <Ri...@jpl.nasa.gov> 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
>> 
>> 
>> 
>> -- 
>> -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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

Hi Mike,

FYI, see my mail to Sheryl the other day:

http://markmail.org/message/wejycqx5tzs5qwoj

Cheers,
Chris


On Oct 14, 2011, at 8:42 AM, Cayanan, Michael D (388J) wrote:

> Hi Rishi,
> 
> Do you know if using version 0.3 (the official released version) will resolve this issue as well?
> 
> Thanks,
> Mike 
> 
> From: "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>
> Reply-To: "user@oodt.apache.org" <us...@oodt.apache.org>
> Date: Wed, 12 Oct 2011 17:32:09 -0700
> To: "user@oodt.apache.org" <us...@oodt.apache.org>
> Subject: Re: Shutting down CAS PGE workflow instances
> 
> Hi Shreyl,
> 
> Thanks for the confirmation!
> 
> I am using 0.4-SNAPSHOT.
> 
> I just checked and 0.3-SNAPSHOT is able to stop workflows via WorkflowInst ID just fine.
> 
> Something new in the latest build must have broke.. will look into it and file an issue if I find some problem in the code.
> 
> thanks -
> rishi
> 
> On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:
> 
>> Which version of the Workflow Manager are you working on?
>> 
>> Try the 0.3-SNAPSHOT version if you working on one of the latest versions of the trunk. I'm not sure if this will fix this.
>> 
>> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com> 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) <Ri...@jpl.nasa.gov> 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
>> 
>> 
>> 
>> -- 
>> -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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>.

Hi Mike,

I have not tested 0.3 (the official version). I would assume it would work just fine though, since this capability was working for a while before the current trunk build in 0.4-SNAPSHOT.

If you have any updates on whether or not this capability works, it would be great if you could share your finding!

Thanks!
rishi

On Oct 14, 2011, at 8:42 AM, Cayanan, Michael D (388J) wrote:

Hi Rishi,

Do you know if using version 0.3 (the official released version) will resolve this issue as well?

Thanks,
Mike

From: "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>>
Reply-To: "user@oodt.apache.org<ma...@oodt.apache.org>" <us...@oodt.apache.org>>
Date: Wed, 12 Oct 2011 17:32:09 -0700
To: "user@oodt.apache.org<ma...@oodt.apache.org>" <us...@oodt.apache.org>>
Subject: Re: Shutting down CAS PGE workflow instances

Hi Shreyl,

Thanks for the confirmation!

I am using 0.4-SNAPSHOT.

I just checked and 0.3-SNAPSHOT is able to stop workflows via WorkflowInst ID just fine.

Something new in the latest build must have broke.. will look into it and file an issue if I find some problem in the code.

thanks -
rishi

On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:

Which version of the Workflow Manager are you working on?

Try the 0.3-SNAPSHOT version if you working on one of the latest versions of the trunk. I'm not sure if this will fix this.

On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com>> 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<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) <Ri...@jpl.nasa.gov>> 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<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<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



--
-Sheryl

Re: Shutting down CAS PGE workflow instances

Posted by "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>.

Hi Mike,

I have not tested 0.3 (the official version). I would assume it would work just fine though, since this capability was working for a while before the current trunk build in 0.4-SNAPSHOT.

If you have any updates on whether or not this capability works, it would be great if you could share your finding!

Thanks!
rishi

On Oct 14, 2011, at 8:42 AM, Cayanan, Michael D (388J) wrote:

Hi Rishi,

Do you know if using version 0.3 (the official released version) will resolve this issue as well?

Thanks,
Mike

From: "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>>
Reply-To: "user@oodt.apache.org<ma...@oodt.apache.org>" <us...@oodt.apache.org>>
Date: Wed, 12 Oct 2011 17:32:09 -0700
To: "user@oodt.apache.org<ma...@oodt.apache.org>" <us...@oodt.apache.org>>
Subject: Re: Shutting down CAS PGE workflow instances

Hi Shreyl,

Thanks for the confirmation!

I am using 0.4-SNAPSHOT.

I just checked and 0.3-SNAPSHOT is able to stop workflows via WorkflowInst ID just fine.

Something new in the latest build must have broke.. will look into it and file an issue if I find some problem in the code.

thanks -
rishi

On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:

Which version of the Workflow Manager are you working on?

Try the 0.3-SNAPSHOT version if you working on one of the latest versions of the trunk. I'm not sure if this will fix this.

On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com>> 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<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) <Ri...@jpl.nasa.gov>> 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<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<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



--
-Sheryl

Re: Shutting down CAS PGE workflow instances

Posted by "Cayanan, Michael D (388J)" <mi...@jpl.nasa.gov>.

Hi Rishi,

Do you know if using version 0.3 (the official released version) will resolve this issue as well?

Thanks,
Mike

From: "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>>
Reply-To: "user@oodt.apache.org<ma...@oodt.apache.org>" <us...@oodt.apache.org>>
Date: Wed, 12 Oct 2011 17:32:09 -0700
To: "user@oodt.apache.org<ma...@oodt.apache.org>" <us...@oodt.apache.org>>
Subject: Re: Shutting down CAS PGE workflow instances

Hi Shreyl,

Thanks for the confirmation!

I am using 0.4-SNAPSHOT.

I just checked and 0.3-SNAPSHOT is able to stop workflows via WorkflowInst ID just fine.

Something new in the latest build must have broke.. will look into it and file an issue if I find some problem in the code.

thanks -
rishi

On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:

Which version of the Workflow Manager are you working on?

Try the 0.3-SNAPSHOT version if you working on one of the latest versions of the trunk. I'm not sure if this will fix this.

On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com>> 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<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) <Ri...@jpl.nasa.gov>> 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<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<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

--
-Sheryl

Re: Shutting down CAS PGE workflow instances

Posted by "Cayanan, Michael D (388J)" <mi...@jpl.nasa.gov>.

Hi Rishi,

Do you know if using version 0.3 (the official released version) will resolve this issue as well?

Thanks,
Mike

From: "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>>
Reply-To: "user@oodt.apache.org<ma...@oodt.apache.org>" <us...@oodt.apache.org>>
Date: Wed, 12 Oct 2011 17:32:09 -0700
To: "user@oodt.apache.org<ma...@oodt.apache.org>" <us...@oodt.apache.org>>
Subject: Re: Shutting down CAS PGE workflow instances

Hi Shreyl,

Thanks for the confirmation!

I am using 0.4-SNAPSHOT.

I just checked and 0.3-SNAPSHOT is able to stop workflows via WorkflowInst ID just fine.

Something new in the latest build must have broke.. will look into it and file an issue if I find some problem in the code.

thanks -
rishi

On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:

Which version of the Workflow Manager are you working on?

Try the 0.3-SNAPSHOT version if you working on one of the latest versions of the trunk. I'm not sure if this will fix this.

On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com>> 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<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) <Ri...@jpl.nasa.gov>> 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<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<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

--
-Sheryl

Re: Shutting down CAS PGE workflow instances

Posted by "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>.

Hi Shreyl,

Thanks for the confirmation!

I am using 0.4-SNAPSHOT.

I just checked and 0.3-SNAPSHOT is able to stop workflows via WorkflowInst ID just fine.

Something new in the latest build must have broke.. will look into it and file an issue if I find some problem in the code.

thanks -
rishi

On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:

Which version of the Workflow Manager are you working on?

Try the 0.3-SNAPSHOT version if you working on one of the latest versions of the trunk. I'm not sure if this will fix this.

On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com>> 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<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) <Ri...@jpl.nasa.gov>> 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<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<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



--
-Sheryl

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

Looks like Rishi answered this one...

Cheers,
Chris

On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:

> Which version of the Workflow Manager are you working on?
> 
> Try the 0.3-SNAPSHOT version if you working on one of the latest versions of the trunk. I'm not sure if this will fix this.
> 
> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com> 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) <Ri...@jpl.nasa.gov> 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
> 
> 
> 
> -- 
> -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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by "Verma, Rishi (388J)" <Ri...@jpl.nasa.gov>.

Hi Shreyl,

Thanks for the confirmation!

I am using 0.4-SNAPSHOT.

I just checked and 0.3-SNAPSHOT is able to stop workflows via WorkflowInst ID just fine.

Something new in the latest build must have broke.. will look into it and file an issue if I find some problem in the code.

thanks -
rishi

On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:

Which version of the Workflow Manager are you working on?

Try the 0.3-SNAPSHOT version if you working on one of the latest versions of the trunk. I'm not sure if this will fix this.

On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com>> 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<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) <Ri...@jpl.nasa.gov>> 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<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<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



--
-Sheryl

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

Looks like Rishi answered this one...

Cheers,
Chris

On Oct 12, 2011, at 5:14 PM, Sheryl John wrote:

> Which version of the Workflow Manager are you working on?
> 
> Try the 0.3-SNAPSHOT version if you working on one of the latest versions of the trunk. I'm not sure if this will fix this.
> 
> On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com> 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) <Ri...@jpl.nasa.gov> 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
> 
> 
> 
> -- 
> -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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by Sheryl John <sh...@gmail.com>.

Which version of the Workflow Manager are you working on?

Try the 0.3-SNAPSHOT version if you working on one of the latest versions of
the trunk. I'm not sure if this will fix this.

On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com> 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) <
> Rishi.Verma@jpl.nasa.gov> 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
>



-- 
-Sheryl

Re: Shutting down CAS PGE workflow instances

Posted by Sheryl John <sh...@gmail.com>.

Oh ok. Will do that. I never bothered to blow away the repo and hence, you
can guess the amount of instances I had. :D

Thanks!

On Thu, Oct 13, 2011 at 6:55 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> 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) <
> chris.a.mattmann@jpl.nasa.gov> 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) <
> Rishi.Verma@jpl.nasa.gov> 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: 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

Re: Shutting down CAS PGE workflow instances

Posted by Sheryl John <sh...@gmail.com>.

Oh ok. Will do that. I never bothered to blow away the repo and hence, you
can guess the amount of instances I had. :D

Thanks!

On Thu, Oct 13, 2011 at 6:55 PM, Mattmann, Chris A (388J) <
chris.a.mattmann@jpl.nasa.gov> wrote:

> 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) <
> chris.a.mattmann@jpl.nasa.gov> 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) <
> Rishi.Verma@jpl.nasa.gov> 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: 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

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

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) <ch...@jpl.nasa.gov> 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) <Ri...@jpl.nasa.gov> 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: 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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

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) <ch...@jpl.nasa.gov> 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) <Ri...@jpl.nasa.gov> 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: 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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by Sheryl John <sh...@gmail.com>.

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) <
chris.a.mattmann@jpl.nasa.gov> 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) <
> Rishi.Verma@jpl.nasa.gov> 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: 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

Re: Shutting down CAS PGE workflow instances

Posted by Sheryl John <sh...@gmail.com>.

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) <
chris.a.mattmann@jpl.nasa.gov> 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) <
> Rishi.Verma@jpl.nasa.gov> 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: 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

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

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) <Ri...@jpl.nasa.gov> 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: 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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by Sheryl John <sh...@gmail.com>.

Which version of the Workflow Manager are you working on?

Try the 0.3-SNAPSHOT version if you working on one of the latest versions of
the trunk. I'm not sure if this will fix this.

On Wed, Oct 12, 2011 at 5:04 PM, Sheryl John <sh...@gmail.com> 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) <
> Rishi.Verma@jpl.nasa.gov> 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
>



-- 
-Sheryl

Re: Shutting down CAS PGE workflow instances

Posted by "Mattmann, Chris A (388J)" <ch...@jpl.nasa.gov>.

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) <Ri...@jpl.nasa.gov> 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: 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
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Re: Shutting down CAS PGE workflow instances

Posted by Sheryl John <sh...@gmail.com>.

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) <
Rishi.Verma@jpl.nasa.gov> 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

Re: Shutting down CAS PGE workflow instances

Posted by Sheryl John <sh...@gmail.com>.

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) <
Rishi.Verma@jpl.nasa.gov> 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