[ 
https://issues.apache.org/jira/browse/OODT-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13551838#comment-13551838
 ] 

Chris A. Mattmann commented on OODT-550:
----------------------------------------

Hey BFost, and Mike, yeah I think this has to do with the 
PackagedWorkflowRepository. What happens is that for dynamic workflows it 
creates temporary new workflow definitions, whose ID are then persisted in the 
workflow instance repo, and then when Mike restarts the WM, and tries to 
getFirstPage, boom error.

I'll get a unit test and patch going for this. 
                
> 'getFirstPage' Command Throws Exception After Restarting Server
> ---------------------------------------------------------------
>
>                 Key: OODT-550
>                 URL: https://issues.apache.org/jira/browse/OODT-550
>             Project: OODT
>          Issue Type: Bug
>          Components: workflow manager
>    Affects Versions: 0.5
>            Reporter: Michael Cayanan
>            Priority: Minor
>             Fix For: 0.6
>
>
> Running the _getFirstPage_ command after restarting the Workflow Manager 
> Server throws an exception. Below shows the set of commands to run to 
> reproduce the issue:
> {code}
> % ./wmgr-client -u http://localhost:9001 --operation --getFirstPage
> Page: [num=0,pageSize=0,totalPages=0]
> % ./wmgr-client -u http://localhost:9001 -en urn:oodt:TestParallel --metaData 
> --key numSeconds 15 -op -se
> Sending event 'urn:oodt:TestParallel'... SUCCESS
> % ./wmgr-client -u http://localhost:9001 --operation --getFirstPage
> Page: [num=1,pageSize=20,totalPages=1]
> Instance: [id=4e5a2d0c-4b47-11e2-977b-c39e66f8f1d5, status=STARTED, 
> currentTask=urn:oodt:IntensiveTask, workflow=Parallel Single Task Processor 
> Intensive Task, wallClockTime=0.09376666666666668, 
> currentTaskWallClockTime=0.0]
> Instance: [id=4e4e6d3b-4b47-11e2-977b-c39e66f8f1d5, status=FINISHED, 
> currentTask=urn:oodt:GoodbyeWorld, workflow=HelloGoodbye, 
> wallClockTime=0.0049, currentTaskWallClockTime=0.0]
> % ./wmgr restart
> -n Shutting down cas workflow manager: 
> OK
> -n Starting cas workflow manager: 
> OK
> Dec 21, 2012 12:21:50 AM 
> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManager loadProperties
> INFO: Loading Workflow Manager Configuration Properties from: 
> [../etc/workflow.properties]
> Dec 21, 2012 12:21:50 AM 
> org.apache.oodt.cas.workflow.engine.ThreadPoolWorkflowEngineFactory 
> getResmgrUrl
> INFO: No Resource Manager URL provided or malformed URL: executing jobs 
> locally. URL: []
> Adding condition: [Timeout Condition] to parent workflow: [TestParallel]
> Dec 21, 2012 12:21:50 AM 
> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManager <init>
> INFO: Workflow Manager started by mcayanan
> % ./wmgr-client -u http://localhost:9001 --operation --getFirstPage
> 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.getFirstPage(XmlRpcWorkflowManagerClient.java:122)
> at 
> org.apache.oodt.cas.workflow.cli.action.GetFirstPageCliAction.execute(GetFirstPageCliAction.java:47)
> at org.apache.oodt.cas.cli.CmdLineUtility.execute(CmdLineUtility.java:331)
> at org.apache.oodt.cas.cli.CmdLineUtility.run(CmdLineUtility.java:187)
> at 
> org.apache.oodt.cas.workflow.system.XmlRpcWorkflowManagerClient.main(XmlRpcWorkflowManagerClient.java:678)
> ERROR: Failed to get first page of workflows : java.lang.Exception: 
> java.lang.NullPointerException
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to