[jira] [Commented] (OOZIE-3592) Do not print misleading System.exit() exception for successful jobs
[ https://issues.apache.org/jira/browse/OOZIE-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056053#comment-17056053 ] Hadoop QA commented on OOZIE-3592: -- Testing JIRA OOZIE-3592 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:green}+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 star imports .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:green}+1{color} the patch adds/modifies 1 testcase(s) {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} Javadoc generation succeeded with the patch .{color:green}+1{color} the patch does not seem to introduce new Javadoc warning(s) {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:red}-1{color} There are [7] new bugs found below threshold in total that must be fixed. .{color:green}+1{color} There are no new bugs found in [fluent-job/fluent-job-api]. .{color:green}+1{color} There are no new bugs found in [docs]. .{color:red}-1{color} There are [6] new bugs found below threshold in [core] that must be fixed, listing only the first [5] ones. .You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html .The top [5] most important SpotBugs errors are: .At BulkJPAExecutor.java:[line 206]: This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection .At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175] .At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199] .This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206] .At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127] .{color:green}+1{color} There are no new bugs found in [sharelib/spark]. .{color:green}+1{color} There are no new bugs found in [sharelib/git]. .{color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. .{color:green}+1{color} There are no new bugs found in [sharelib/hive2]. .{color:green}+1{color} There are no new bugs found in [sharelib/streaming]. .{color:green}+1{color} There are no new bugs found in [sharelib/pig]. .{color:red}-1{color} There are [1] new bugs found below threshold in [sharelib/oozie] that must be fixed. .You can find the SpotBugs diff here (look for the red and orange ones): sharelib/oozie/findbugs-new.html .The most important SpotBugs errors are: .At ShellMain.java:[line 93]: This usage of java/lang/ProcessBuilder.(Ljava/util/List;)V can be vulnerable to Command Injection .At ShellMain.java:[line 91]: At ShellMain.java:[line 90] .At ShellMain.java:[line 92] .{color:green}+1{color} There are no new bugs found in [sharelib/hive]. .{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. .{color:green}+1{color} There are no new bugs found in [sharelib/distcp]. .{color:green}+1{color} There are no new bugs found in [tools]. .{color:orange}0{color} There are [4] new bugs found in [server] that would be nice to have fixed. .You can find the SpotBugs diff here: server/findbugs-new.html .{color:green}+1{color} There are no new bugs found in [client]. .{color:green}+1{color} There are no new bugs found in [examples]. .{color:green}+1{color} There are no new bugs found in [webapp]. {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:green}+1 TESTS{color} .Tests run: 3209 .{color:orange}Tests failed at first run:{color} TestBlockingInputStream#testFastWritingBlockingInputStream TestBlockingInputStream#testLimitedWritingBlockingInputStream .For the complete list of flaky tests, see TEST-SUMMARY-FULL files. {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:green}+1 MODERNIZER{color} {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/
[jira] [Commented] (OOZIE-3592) Do not print misleading System.exit() exception for successful jobs
[ https://issues.apache.org/jira/browse/OOZIE-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055954#comment-17055954 ] Hadoop QA commented on OOZIE-3592: -- PreCommit-OOZIE-Build started > Do not print misleading System.exit() exception for successful jobs > --- > > Key: OOZIE-3592 > URL: https://issues.apache.org/jira/browse/OOZIE-3592 > Project: Oozie > Issue Type: Bug >Affects Versions: 5.2.0 >Reporter: Mate Juhasz >Assignee: Mate Juhasz >Priority: Major > Fix For: trunk > > Attachments: OOZIE-3592-v1.patch, OOZIE-3592-v2.patch, > OOZIE-3592-v3.patch > > > The following exception is logged by Oozie due to System.exit() calls in > application JVM-s even after successful workflow actions: > {noformat} > Hadoop Job IDs executed by Sqoop: job_1583161376812_0018 > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.apache.oozie.action.hadoop.LauncherAM.runActionMain(LauncherAM.java:413) > at > org.apache.oozie.action.hadoop.LauncherAM.access$400(LauncherAM.java:55) > at org.apache.oozie.action.hadoop.LauncherAM$2.run(LauncherAM.java:226) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1876) > at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:220) > at org.apache.oozie.action.hadoop.LauncherAM$1.run(LauncherAM.java:156) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1876) > at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:144) > Caused by: java.lang.SecurityException: Intercepted System.exit(0) > at > org.apache.oozie.action.hadoop.security.LauncherSecurityManager.checkExit(LauncherSecurityManager.java:57) > at java.lang.Runtime.exit(Runtime.java:107) > at java.lang.System.exit(System.java:971) > at org.apache.sqoop.Sqoop.main(Sqoop.java:260) > at > org.apache.oozie.action.hadoop.SqoopMain.runSqoopJob(SqoopMain.java:221) > at org.apache.oozie.action.hadoop.SqoopMain.run(SqoopMain.java:206) > at > org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:107) > at org.apache.oozie.action.hadoop.SqoopMain.main(SqoopMain.java:52) > ... 16 more > Intercepting System.exit(0) > {noformat} > Typically happens in Sqoop actions. This can be very misleading for users as > they may suspect that some error has occurred even if their yarn application > and Oozie workflow has been marked as succeeded. > The "error" is already ignored by Oozie when the System.exit code is 0, but > we should not print either this exception in such cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3592) Do not print misleading System.exit() exception for successful jobs
[ https://issues.apache.org/jira/browse/OOZIE-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055230#comment-17055230 ] Hadoop QA commented on OOZIE-3592: -- Testing JIRA OOZIE-3592 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:green}+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 star imports .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:green}+1{color} the patch adds/modifies 1 testcase(s) {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} Javadoc generation succeeded with the patch .{color:green}+1{color} the patch does not seem to introduce new Javadoc warning(s) {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:red}-1{color} There are [7] new bugs found below threshold in total that must be fixed. .{color:green}+1{color} There are no new bugs found in [webapp]. .{color:green}+1{color} There are no new bugs found in [fluent-job/fluent-job-api]. .{color:green}+1{color} There are no new bugs found in [sharelib/streaming]. .{color:green}+1{color} There are no new bugs found in [sharelib/spark]. .{color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. .{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. .{color:green}+1{color} There are no new bugs found in [sharelib/git]. .{color:green}+1{color} There are no new bugs found in [sharelib/distcp]. .{color:green}+1{color} There are no new bugs found in [sharelib/hive]. .{color:green}+1{color} There are no new bugs found in [sharelib/pig]. .{color:green}+1{color} There are no new bugs found in [sharelib/hive2]. .{color:orange}0{color} There are [1] new bugs found in [sharelib/oozie] that would be nice to have fixed. .You can find the SpotBugs diff here: sharelib/oozie/findbugs-new.html .{color:green}+1{color} There are no new bugs found in [tools]. .{color:green}+1{color} There are no new bugs found in [server]. .{color:green}+1{color} There are no new bugs found in [examples]. .{color:green}+1{color} There are no new bugs found in [docs]. .{color:green}+1{color} There are no new bugs found in [client]. .{color:red}-1{color} There are [7] new bugs found below threshold in [core] that must be fixed, listing only the first [5] ones. .You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html .The top [5] most important SpotBugs errors are: .At BulkJPAExecutor.java:[line 206]: This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection .At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175] .At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199] .This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206] .At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127] {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:green}+1 TESTS{color} .Tests run: 3210 .{color:orange}Tests failed at first run:{color} TestBlockingInputStream#testFastWritingBlockingInputStream TestBlockingInputStream#testLimitedWritingBlockingInputStream .For the complete list of flaky tests, see TEST-SUMMARY-FULL files. {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:green}+1 MODERNIZER{color} {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/PreCommit-OOZIE-Build/1315/ > Do not print misleading System.exit() exception for successful jobs > --- > > Key: OOZIE-3592 > URL: https://issues.apache.org/jira/browse/OOZIE-3592 > Project: Oozie > Issue Type: Bug >Affects Versions: 5.2.0 >Reporter: Mate Juhasz >As
[jira] [Commented] (OOZIE-3592) Do not print misleading System.exit() exception for successful jobs
[ https://issues.apache.org/jira/browse/OOZIE-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055087#comment-17055087 ] Hadoop QA commented on OOZIE-3592: -- PreCommit-OOZIE-Build started > Do not print misleading System.exit() exception for successful jobs > --- > > Key: OOZIE-3592 > URL: https://issues.apache.org/jira/browse/OOZIE-3592 > Project: Oozie > Issue Type: Bug >Affects Versions: 5.2.0 >Reporter: Mate Juhasz >Assignee: Mate Juhasz >Priority: Major > Fix For: trunk > > Attachments: OOZIE-3592-v1.patch, OOZIE-3592-v2.patch > > > The following exception is logged by Oozie due to System.exit() calls in > application JVM-s even after successful workflow actions: > {noformat} > Hadoop Job IDs executed by Sqoop: job_1583161376812_0018 > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.apache.oozie.action.hadoop.LauncherAM.runActionMain(LauncherAM.java:413) > at > org.apache.oozie.action.hadoop.LauncherAM.access$400(LauncherAM.java:55) > at org.apache.oozie.action.hadoop.LauncherAM$2.run(LauncherAM.java:226) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1876) > at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:220) > at org.apache.oozie.action.hadoop.LauncherAM$1.run(LauncherAM.java:156) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1876) > at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:144) > Caused by: java.lang.SecurityException: Intercepted System.exit(0) > at > org.apache.oozie.action.hadoop.security.LauncherSecurityManager.checkExit(LauncherSecurityManager.java:57) > at java.lang.Runtime.exit(Runtime.java:107) > at java.lang.System.exit(System.java:971) > at org.apache.sqoop.Sqoop.main(Sqoop.java:260) > at > org.apache.oozie.action.hadoop.SqoopMain.runSqoopJob(SqoopMain.java:221) > at org.apache.oozie.action.hadoop.SqoopMain.run(SqoopMain.java:206) > at > org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:107) > at org.apache.oozie.action.hadoop.SqoopMain.main(SqoopMain.java:52) > ... 16 more > Intercepting System.exit(0) > {noformat} > Typically happens in Sqoop actions. This can be very misleading for users as > they may suspect that some error has occurred even if their yarn application > and Oozie workflow has been marked as succeeded. > The "error" is already ignored by Oozie when the System.exit code is 0, but > we should not print either this exception in such cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3592) Do not print misleading System.exit() exception for successful jobs
[ https://issues.apache.org/jira/browse/OOZIE-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053488#comment-17053488 ] Hadoop QA commented on OOZIE-3592: -- Testing JIRA OOZIE-3592 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 star imports .{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} Javadoc generation succeeded with the patch .{color:green}+1{color} the patch does not seem to introduce new Javadoc warning(s) {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:red}-1{color} There are [7] new bugs found below threshold in total that must be fixed. .{color:green}+1{color} There are no new bugs found in [fluent-job/fluent-job-api]. .{color:green}+1{color} There are no new bugs found in [docs]. .{color:red}-1{color} There are [6] new bugs found below threshold in [core] that must be fixed, listing only the first [5] ones. .You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html .The top [5] most important SpotBugs errors are: .At BulkJPAExecutor.java:[line 206]: This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection .At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175] .At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199] .This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206] .At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127] .{color:green}+1{color} There are no new bugs found in [sharelib/spark]. .{color:green}+1{color} There are no new bugs found in [sharelib/git]. .{color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. .{color:green}+1{color} There are no new bugs found in [sharelib/hive2]. .{color:green}+1{color} There are no new bugs found in [sharelib/streaming]. .{color:green}+1{color} There are no new bugs found in [sharelib/pig]. .{color:red}-1{color} There are [1] new bugs found below threshold in [sharelib/oozie] that must be fixed. .You can find the SpotBugs diff here (look for the red and orange ones): sharelib/oozie/findbugs-new.html .The most important SpotBugs errors are: .At ErrorHolder.java:[line 64]: Possible information exposure through an error message .{color:green}+1{color} There are no new bugs found in [sharelib/hive]. .{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. .{color:green}+1{color} There are no new bugs found in [sharelib/distcp]. .{color:green}+1{color} There are no new bugs found in [tools]. .{color:orange}0{color} There are [4] new bugs found in [server] that would be nice to have fixed. .You can find the SpotBugs diff here: server/findbugs-new.html .{color:green}+1{color} There are no new bugs found in [client]. .{color:green}+1{color} There are no new bugs found in [examples]. .{color:green}+1{color} There are no new bugs found in [webapp]. {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: 3209 .Tests failed : 0 .Tests in error : 2 .Tests timed out : 0 {color:red}-1{color} [ERROR] There are [2] test errors in [sharelib]. Listing only the first [5] ones testActionThrowsLauncherException:org.apache.oozie.action.hadoop.TestLauncherAM testActionThrowsSecurityExceptionWithExitCode1:org.apache.oozie.action.hadoop.TestLauncherAM Check console output for the full list of errors/failures .{color:orange}Tests failed at first run:{color} TestBlockingInputStream#testLimitedWritingBlockingInputStream .For the complete list of flaky tests, see TEST-SUMMARY-FULL files. {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {
[jira] [Commented] (OOZIE-3592) Do not print misleading System.exit() exception for successful jobs
[ https://issues.apache.org/jira/browse/OOZIE-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053399#comment-17053399 ] Hadoop QA commented on OOZIE-3592: -- PreCommit-OOZIE-Build started > Do not print misleading System.exit() exception for successful jobs > --- > > Key: OOZIE-3592 > URL: https://issues.apache.org/jira/browse/OOZIE-3592 > Project: Oozie > Issue Type: Bug >Affects Versions: 5.2.0 >Reporter: Mate Juhasz >Assignee: Mate Juhasz >Priority: Major > Fix For: trunk > > Attachments: OOZIE-3592-v1.patch > > > The following exception is logged by Oozie due to System.exit() calls in > application JVM-s even after successful workflow actions: > {noformat} > Hadoop Job IDs executed by Sqoop: job_1583161376812_0018 > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.apache.oozie.action.hadoop.LauncherAM.runActionMain(LauncherAM.java:413) > at > org.apache.oozie.action.hadoop.LauncherAM.access$400(LauncherAM.java:55) > at org.apache.oozie.action.hadoop.LauncherAM$2.run(LauncherAM.java:226) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1876) > at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:220) > at org.apache.oozie.action.hadoop.LauncherAM$1.run(LauncherAM.java:156) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1876) > at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:144) > Caused by: java.lang.SecurityException: Intercepted System.exit(0) > at > org.apache.oozie.action.hadoop.security.LauncherSecurityManager.checkExit(LauncherSecurityManager.java:57) > at java.lang.Runtime.exit(Runtime.java:107) > at java.lang.System.exit(System.java:971) > at org.apache.sqoop.Sqoop.main(Sqoop.java:260) > at > org.apache.oozie.action.hadoop.SqoopMain.runSqoopJob(SqoopMain.java:221) > at org.apache.oozie.action.hadoop.SqoopMain.run(SqoopMain.java:206) > at > org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:107) > at org.apache.oozie.action.hadoop.SqoopMain.main(SqoopMain.java:52) > ... 16 more > Intercepting System.exit(0) > {noformat} > Typically happens in Sqoop actions. This can be very misleading for users as > they may suspect that some error has occurred even if their yarn application > and Oozie workflow has been marked as succeeded. > The "error" is already ignored by Oozie when the System.exit code is 0, but > we should not print either this exception in such cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3592) Do not print misleading System.exit() exception for successful jobs
[ https://issues.apache.org/jira/browse/OOZIE-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053394#comment-17053394 ] Mate Juhasz commented on OOZIE-3592: Added an initial patch, but I still owe with unit tests > Do not print misleading System.exit() exception for successful jobs > --- > > Key: OOZIE-3592 > URL: https://issues.apache.org/jira/browse/OOZIE-3592 > Project: Oozie > Issue Type: Bug >Affects Versions: 5.2.0 >Reporter: Mate Juhasz >Assignee: Mate Juhasz >Priority: Major > Fix For: trunk > > Attachments: OOZIE-3592-v1.patch > > > The following exception is logged by Oozie due to System.exit() calls in > application JVM-s even after successful workflow actions: > {noformat} > Hadoop Job IDs executed by Sqoop: job_1583161376812_0018 > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.apache.oozie.action.hadoop.LauncherAM.runActionMain(LauncherAM.java:413) > at > org.apache.oozie.action.hadoop.LauncherAM.access$400(LauncherAM.java:55) > at org.apache.oozie.action.hadoop.LauncherAM$2.run(LauncherAM.java:226) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1876) > at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:220) > at org.apache.oozie.action.hadoop.LauncherAM$1.run(LauncherAM.java:156) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1876) > at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:144) > Caused by: java.lang.SecurityException: Intercepted System.exit(0) > at > org.apache.oozie.action.hadoop.security.LauncherSecurityManager.checkExit(LauncherSecurityManager.java:57) > at java.lang.Runtime.exit(Runtime.java:107) > at java.lang.System.exit(System.java:971) > at org.apache.sqoop.Sqoop.main(Sqoop.java:260) > at > org.apache.oozie.action.hadoop.SqoopMain.runSqoopJob(SqoopMain.java:221) > at org.apache.oozie.action.hadoop.SqoopMain.run(SqoopMain.java:206) > at > org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:107) > at org.apache.oozie.action.hadoop.SqoopMain.main(SqoopMain.java:52) > ... 16 more > Intercepting System.exit(0) > {noformat} > Typically happens in Sqoop actions. This can be very misleading for users as > they may suspect that some error has occurred even if their yarn application > and Oozie workflow has been marked as succeeded. > The "error" is already ignored by Oozie when the System.exit code is 0, but > we should not print either this exception in such cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3592) Do not print misleading System.exit() exception for successful jobs
[ https://issues.apache.org/jira/browse/OOZIE-3592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17052268#comment-17052268 ] Andras Salamon commented on OOZIE-3592: --- Yes, this is a rather annoying, would be great to fix this and only print out the exception if we really have a problem. > Do not print misleading System.exit() exception for successful jobs > --- > > Key: OOZIE-3592 > URL: https://issues.apache.org/jira/browse/OOZIE-3592 > Project: Oozie > Issue Type: Bug >Affects Versions: 5.2.0 >Reporter: Mate Juhasz >Assignee: Mate Juhasz >Priority: Major > Fix For: trunk > > > The following exception is logged by Oozie due to System.exit() calls in > application JVM-s even after successful workflow actions: > {noformat} > Hadoop Job IDs executed by Sqoop: job_1583161376812_0018 > java.lang.reflect.InvocationTargetException > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.apache.oozie.action.hadoop.LauncherAM.runActionMain(LauncherAM.java:413) > at > org.apache.oozie.action.hadoop.LauncherAM.access$400(LauncherAM.java:55) > at org.apache.oozie.action.hadoop.LauncherAM$2.run(LauncherAM.java:226) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1876) > at org.apache.oozie.action.hadoop.LauncherAM.run(LauncherAM.java:220) > at org.apache.oozie.action.hadoop.LauncherAM$1.run(LauncherAM.java:156) > at java.security.AccessController.doPrivileged(Native Method) > at javax.security.auth.Subject.doAs(Subject.java:422) > at > org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1876) > at org.apache.oozie.action.hadoop.LauncherAM.main(LauncherAM.java:144) > Caused by: java.lang.SecurityException: Intercepted System.exit(0) > at > org.apache.oozie.action.hadoop.security.LauncherSecurityManager.checkExit(LauncherSecurityManager.java:57) > at java.lang.Runtime.exit(Runtime.java:107) > at java.lang.System.exit(System.java:971) > at org.apache.sqoop.Sqoop.main(Sqoop.java:260) > at > org.apache.oozie.action.hadoop.SqoopMain.runSqoopJob(SqoopMain.java:221) > at org.apache.oozie.action.hadoop.SqoopMain.run(SqoopMain.java:206) > at > org.apache.oozie.action.hadoop.LauncherMain.run(LauncherMain.java:107) > at org.apache.oozie.action.hadoop.SqoopMain.main(SqoopMain.java:52) > ... 16 more > Intercepting System.exit(0) > {noformat} > Typically happens in Sqoop actions. This can be very misleading for users as > they may suspect that some error has occurred even if their yarn application > and Oozie workflow has been marked as succeeded. > The "error" is already ignored by Oozie when the System.exit code is 0, but > we should not print either this exception in such cases. -- This message was sent by Atlassian Jira (v8.3.4#803005)