[ https://issues.apache.org/jira/browse/OOZIE-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365395#comment-15365395 ]
Hadoop QA commented on OOZIE-2581: ---------------------------------- Testing JIRA OOZIE-2581 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: 1787 . Tests failed: 2 . Tests errors: 0 . The patch failed the following testcases: . testMessage_withMixedStatus(org.apache.oozie.command.coord.TestAbandonedCoordChecker) . testWFNotificationTimeout(org.apache.oozie.command.wf.TestWorkflowNotificationXCommand) {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/3026/ > Oozie should reset SecurityManager in finally block > --------------------------------------------------- > > Key: OOZIE-2581 > URL: https://issues.apache.org/jira/browse/OOZIE-2581 > Project: Oozie > Issue Type: Bug > Reporter: Satish Subhashrao Saley > Assignee: Satish Subhashrao Saley > Attachments: OOZIE-2581-1.patch, OOZIE-2581-2.patch > > > [~jlowe] found lot of lingering oozie launcher AMs which hung around 10 mins > after successful completion and then jvm killed due to timeout. This happens > when user code launches non-daemon threads, but mapreduce code does a > System.exit() to avoid this from happening. Oozie does need the > LauncherSecurityManager to capture exit codes when user applications do > System.exit() . But it should reset it back to the originial security manager > in the finally block so that AM code can proceed as expected in uber mode. > {code} > 2016-05-12 12:26:48,514 INFO [Thread-107] org.apache.hadoop.util.ExitUtil: > Exiting with status 1 > 2016-05-12 12:26:48,514 ERROR [Thread-107] > org.apache.hadoop.yarn.YarnUncaughtExceptionHandler: Thread > Thread[Thread-107,5,main] threw an Exception. > java.lang.SecurityException: Intercepted System.exit(1) > at > org.apache.oozie.action.hadoop.LauncherSecurityManager.checkExit(LauncherMapper.java:637) > at java.lang.Runtime.exit(Runtime.java:107) > at java.lang.System.exit(System.java:971) > at org.apache.hadoop.util.ExitUtil.terminate(ExitUtil.java:133) > at org.apache.hadoop.util.ExitUtil.terminate(ExitUtil.java:170) > at > org.apache.hadoop.mapreduce.v2.app.MRAppMaster.exitMRAppMaster(MRAppMaster.java:655) > at > org.apache.hadoop.mapreduce.v2.app.MRAppMaster.shutDownJob(MRAppMaster.java:636) > at > org.apache.hadoop.mapreduce.v2.app.MRAppMaster$JobFinishEventHandler$1.run(MRAppMaster.java:676) > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)