[jira] [Resolved] (OOZIE-1571) Getting Optimistic Lock Exceptions when trying to query for status of Job using client api

["Dénes Bodó (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OOZIE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dénes Bodó resolved OOZIE-1571.
-------------------------------
    Resolution: Cannot Reproduce

This ticket seems abandoned. If you feel that this still an issue in Oozie 5 then please reopen.

> Getting Optimistic Lock Exceptions when trying to query for status of Job using client api
> ------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-1571
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1571
>             Project: Oozie
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 3.3.0
>         Environment: Linux Redhat
>            Reporter: Giridhar Addepalli
>            Priority: Major
>              Labels: newbie
>         Attachments: oozie.log-2013-09-22-15
>
>
> http://archive.cloudera.com/cdh/3/oozie/DG_Examples.html
> I was following example from above webpage to submit job to oozie and wait for its completion
> // submit and start the workflow job
>     String jobId = wc.run(conf);
>     System.out.println("Workflow job submitted");
> .
>     // wait until the workflow job finishes printing the status every 10 seconds
>     while (wc.getJobInfo(jobId).getStatus() == Workflow.Status.RUNNING) {
>         System.out.println("Workflow job running ...");
>         Thread.sleep(10 * 1000);
>     }
> Occassionally, i am seeing following exception
> E0605 : E0605: Action does not exist [<openjpa-2.1.0-r422266:1071316 nonfatal store error> org.apache.openjpa.persistence.OptimisticLockException: Unable to obtain an object lock on "null".]
> 	at org.apache.oozie.client.OozieClient.handleError(OozieClient.java:445)
> 	at org.apache.oozie.client.OozieClient$JobInfo.call(OozieClient.java:658)
> 	at org.apache.oozie.client.OozieClient$JobInfo.call(OozieClient.java:642)
> 	at org.apache.oozie.client.OozieClient$ClientCallable.call(OozieClient.java:416)
> 	at org.apache.oozie.client.OozieClient.getJobInfo(OozieClient.java:705)
> 	at org.apache.oozie.client.OozieClient.getJobInfo(OozieClient.java:692)
> 	at com.walmartlabs.dare.oozie.OozieExecutionManager.submitToOozie(OozieExecutionManager.java:134)
> 	at com.walmartlabs.dare.oozie.OozieExecutionManager.runExecTask(OozieExecutionManager.java:72)
> 	at com.codeminders.hamake.execution.AbstractExecutionManager.runTask(AbstractExecutionManager.java:180)
> 	at com.codeminders.hamake.execution.AbstractExecutionManager.access$000(AbstractExecutionManager.java:17)
> 	at com.codeminders.hamake.execution.AbstractExecutionManager$TaskExecutionInfo.run(AbstractExecutionManager.java:47)
> 	at java.lang.Thread.run(Thread.java:662)
> 134th line in our code is ::
> Status jobStatus = oozieClient.getJobInfo(jobId).getStatus();
> I see from webconsole that corresponding oozie job got completed successfully.
> Here is Virag's comment on oozie user group ::
> "
> This looks like a bug, so please create a JIRA and attach the log file there.
> This optimistic lock exception shouldn't be happening as Oozie doesn't use optimistic locking. 
> For now, it might be safe for you to ignore this exception. getJobInfo() for wf job also reads the wf action entity but it might be updated during read which seems to cause that exception.
> As you are only interested in getJobInfo().getStatus(), you can ignore it.
> "
> Thanks,
> Giridhar.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)