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

Hadoop QA commented on OOZIE-1932:
----------------------------------

Testing JIRA OOZIE-1932

Cleaning local git workspace

----------------------------

{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.    {color:green}+1{color} the patch does not introduce any @author tags
.    {color:green}+1{color} the patch does not introduce any tabs
.    {color:green}+1{color} the patch does not introduce any trailing spaces
.    {color:green}+1{color} the patch does not introduce any line longer than 
132
.    {color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.    {color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.    {color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.    {color:green}+1{color} HEAD compiles
.    {color:green}+1{color} patch compiles
.    {color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.    {color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.    {color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.    Tests run: 1508
.    Tests failed: 1
.    Tests errors: 0

.    The patch failed the following testcases:

.      
testNone(org.apache.oozie.command.coord.TestCoordActionInputCheckXCommand)

{color:green}+1 DISTRO{color}
.    {color:green}+1{color} distro tarball builds with the patch 

----------------------------
{color:red}*-1 Overall result, please check the reported -1(s)*{color}


The full output of the test-patch run is available at

.   https://builds.apache.org/job/oozie-trunk-precommit-build/1685/

> Services should load CallableQueueService after MemoryLocksService
> ------------------------------------------------------------------
>
>                 Key: OOZIE-1932
>                 URL: https://issues.apache.org/jira/browse/OOZIE-1932
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: trunk
>            Reporter: Mona Chitnis
>            Assignee: Mona Chitnis
>             Fix For: 4.1.0
>
>         Attachments: OOZIE-1932-2.patch, OOZIE-1932-addendum.patch, 
> OOZIE-1932.patch
>
>
> This is not a problem during startup but is during shutdown, as services are 
> destroyed in reverse order of initialization. Hence, when MemoryLocksService 
> destroy sets it to null, and commands are still executing due to 
> CallableQueueService still active, they all encounter NPEs during locking. 
> This is a simple fix in oozie-default.xml to set MemoryLocksService before in 
> the order of services loading.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to