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

Hadoop QA commented on OOZIE-934:
---------------------------------

Testing JIRA OOZIE-934

Cleaning local svn workspace

{code}
----------------------------

+1 PATCH_APPLIES
   CLEAN cleaned target directories
-1 RAW_PATCH_ANALYSIS
    +1 the patch does not introduce any @author tags
    +1 the patch does not introduce any tabs
    +1 the patch does not introduce any trailing spaces
    -1 the patch contains 1 line(s) longer than 132 characters
    -1 the patch does not add/modify any testcase
+1 RAT
    +1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
    +1 the patch does not seem to introduce new Javadoc warnings
-1 COMPILE
    -1 HEAD does not compile
    -1 patch does not compile
    +1 the patch does not seem to introduce new javac warnings
+1 BACKWARDS_COMPATIBILITY
    +1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
    +1 the patch does not modify JPA files
-1 TESTS - patch does not compile, cannot run testcases
   Tests run: 0
   Tests failures: 0
   Tests errors: 0
-1 DISTRO
    -1 distro tarball fails with the patch

----------------------------
{code}

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

   https://builds.apache.org/job/oozie-trunk-precommit-build/47/
                
> Exception reporting during Services startup is inadequate
> ---------------------------------------------------------
>
>                 Key: OOZIE-934
>                 URL: https://issues.apache.org/jira/browse/OOZIE-934
>             Project: Oozie
>          Issue Type: Bug
>    Affects Versions: trunk, 3.2.1
>            Reporter: Mona Chitnis
>            Assignee: Mona Chitnis
>              Labels: oozie, service
>             Fix For: 3.2.0, trunk
>
>         Attachments: OOZIE-934.patch, OOZIE-934v3.patch
>
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> During Oozie server startup, some of the services e.g. ActionService, if they 
> encounter an exception during initialization, the exception is not propagated 
> to the caller. As a result, shutdown occurs without any leads in the logs. 
> Exception handling needs to be improved for services init.

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

        

Reply via email to