[jira] [Resolved] (OOZIE-1478) Some commands display incorrect LogInfo in acquireLock statements

["Mona Chitnis (JIRA)" <ji...@apache.org>]

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

Mona Chitnis resolved OOZIE-1478.
---------------------------------

    Resolution: Invalid

Issue not seen anymore
                
> Some commands display incorrect LogInfo in acquireLock statements
> -----------------------------------------------------------------
>
>                 Key: OOZIE-1478
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1478
>             Project: Oozie
>          Issue Type: Sub-task
>    Affects Versions: trunk, 4.0.0
>            Reporter: Mona Chitnis
>            Assignee: Mona Chitnis
>             Fix For: trunk, 4.0.0
>
>
> In XCommand execute(), the order is this
> eagerLoadState()
> eagerVerifyPreCondition()
> acquireLock()
> loadState()
> verifyPreCondition()
> All of these generate Log statements with JOB and ACTION ids populated. However in most commands, loadState() is where LogInfo is updated with the correct JOB and ACTION ids, hence preceding statements can show old LogInfo of some other job.
> The resetPrefix() is not working as expected.

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