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

Posted to dev@oozie.apache.org by "Virag Kothari (JIRA)" <ji...@apache.org> on 2012/05/13 06:43:25 UTC

[jira] [Updated] (OOZIE-651) Coordinator rerun fails due to NPE in some cases

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

Virag Kothari updated OOZIE-651:
--------------------------------


For the patch committed in trunk with this JIRA ID (also available under the same JIRA ID in Apache ReviewBoard system), I grant license to ASF for inclusion in ASF works (as per the Apache License §5) 
                
> Coordinator rerun fails due to NPE in some cases
> ------------------------------------------------
>
>                 Key: OOZIE-651
>                 URL: https://issues.apache.org/jira/browse/OOZIE-651
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Virag Kothari
>            Assignee: Virag Kothari
>             Fix For: 3.2.0
>
>
> CoordinatorActionInfo coordInfo = coordEngine.reRun(jobId, rerunType, scope, Boolean.valueOf(refresh),
>                     Boolean.valueOf(noCleanup));
> coordActions = coordInfo.getCoordActions();
> The Coordinator rerun command requires to acquire the lock before it executes. If it cant get the lock, then it is queued. In this case the return value, the coordInfo, is null. Trying to access the coordInfo causes NPE in such a case.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira