[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (104 issues) Subscriber: ooziedaily Key Summary OOZIE-3716 Invocation of Main class completed Message is skipped when LauncherSecurityManager calls system exit https://issues.apache.org/jira/browse/OOZIE-3716 OOZIE-3715 Fix fork out more than one transitions submit , one transition submit fail can't execute KillXCommand https://issues.apache.org/jira/browse/OOZIE-3715 OOZIE-3687 Fix Oozie client always using the current system username instead the one specified by the user (e.g.: via kerberos or via explicit basic authentication) https://issues.apache.org/jira/browse/OOZIE-3687 OOZIE-3680 Add default value to custom configuration of all the supported file systems in Oozie https://issues.apache.org/jira/browse/OOZIE-3680 OOZIE-3663 Upgrade Apache Xerces Java to 2.12.2 https://issues.apache.org/jira/browse/OOZIE-3663 OOZIE-3654 update to httpclient 4.5.13 https://issues.apache.org/jira/browse/OOZIE-3654 OOZIE-3635 Reduce nest of code in RecoveryService https://issues.apache.org/jira/browse/OOZIE-3635 OOZIE-3623 Fix Typos in Distro Assembly https://issues.apache.org/jira/browse/OOZIE-3623 OOZIE-3621 Make TestECPolicyDisabler work with Hadoop 3 https://issues.apache.org/jira/browse/OOZIE-3621 OOZIE-3620 hadoopId is not sent to eventHandlerService (listener) for workflow action events https://issues.apache.org/jira/browse/OOZIE-3620 OOZIE-3609 Zookeeper SSL/TLS support https://issues.apache.org/jira/browse/OOZIE-3609 OOZIE-3596 When the SSH action is killed, it must be changed to the kill command that can terminate the related subprocess. https://issues.apache.org/jira/browse/OOZIE-3596 OOZIE-3568 Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean https://issues.apache.org/jira/browse/OOZIE-3568 OOZIE-3567 Oozie ShellAction should support absolute bash file path https://issues.apache.org/jira/browse/OOZIE-3567 OOZIE-3560 IDEA shows have some error in index.jsp https://issues.apache.org/jira/browse/OOZIE-3560 OOZIE-3554 Add asf.yaml to git repo https://issues.apache.org/jira/browse/OOZIE-3554 OOZIE-3545 Upgrade jQuery https://issues.apache.org/jira/browse/OOZIE-3545 OOZIE-3482 Fix bug in CoordSubmitXCommand#validateCoordinatorJob https://issues.apache.org/jira/browse/OOZIE-3482 OOZIE-3480 Add windowactionstatus metrics in DBLiteWorkflowStoreService https://issues.apache.org/jira/browse/OOZIE-3480 OOZIE-3461 CoordMaterializeTriggerService code cleanup https://issues.apache.org/jira/browse/OOZIE-3461 OOZIE-3449 Make spark-2 as the default profile https://issues.apache.org/jira/browse/OOZIE-3449 OOZIE-3447 Run test case in local : It shows oozie-hsqldb-orm.xml exception https://issues.apache.org/jira/browse/OOZIE-3447 OOZIE-3434 Filtering for invalid jobtype should give error message https://issues.apache.org/jira/browse/OOZIE-3434 OOZIE-3418 Upgrade to Guava 27 https://issues.apache.org/jira/browse/OOZIE-3418 OOZIE-3404 The env variable of SPARK_HOME needs to be set when running pySpark https://issues.apache.org/jira/browse/OOZIE-3404 OOZIE-3375 Can't use empty in coordinator https://issues.apache.org/jira/browse/OOZIE-3375 OOZIE-3367 Using && in EL expressions in oozie bundle.xml files generates parse errors https://issues.apache.org/jira/browse/OOZIE-3367 OOZIE-3366 Update workflow status and subworkflow status on suspend command https://issues.apache.org/jira/browse/OOZIE-3366 OOZIE-3364 Rerunning Oozie bundle jobs starts the coordinators in indeterminate order https://issues.apache.org/jira/browse/OOZIE-3364 OOZIE-3362 When killed, SSH action should kill the spawned processes on target host https://issues.apache.org/jira/browse/OOZIE-3362 OOZIE-3335 Cleanup parseFilter methods https://issues.apache.org/jira/browse/OOZIE-3335 OOZIE-3328 Create Hive compatibility action executor to run hive actions using beeline https://issues.apache.org/jira/browse/OOZIE-3328 OOZIE-3319 Log SSH action callback error output https://issues.apache.org/jira/browse/OOZIE-3319 OOZIE-3301 Update NOTICE file https://issues.apache.org/jira/browse/OOZIE-3301 OOZIE-3274 Remove slf4j https://issues.apache.org/jira/browse/OOZIE-3274 OOZIE-3266 Coord action rerun support RERUN_SKIP_NODES option https://issues.apache.org/jira/browse/OOZIE-3266 OOZIE-3256 refactor OozieCLI class https://issues.apache.org/jira/browse/OOZIE-3256 OOZIE-3196 Authorization: restrict world readability by user https://issues.apache.org/jira/browse/OOZIE-3196
[jira] [Commented] (OOZIE-3716) Invocation of Main class completed Message is skipped when LauncherSecurityManager calls system exit
[
https://issues.apache.org/jira/browse/OOZIE-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713860#comment-17713860
]
Hadoop QA commented on OOZIE-3716:
--
Testing JIRA OOZIE-3716
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 [5] new bugs found below threshold in total that
must be fixed.
.{color:red}-1{color} There are [5] new bugs found below threshold in
[core] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The 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 [client].
.{color:green}+1{color} There are no new bugs found in [docs].
.{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 [server].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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/spark].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{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/streaming].
.{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/sqoop].
.{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/git].
{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: 3259
{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://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/208/
> Invocation of Main class completed Message is skipped when
> LauncherSecurityManager calls system exit
>
>
> Key: OOZIE-3716
> URL: https://issues.apache.org/jira/browse/OOZIE-3716
> Project: Oozie
> Issue Type: Wish
> Components: action
>Affects Versions: 5.0.0, 5.1.0, 5.2.0, 5.3.0, 5.2.1
>Reporter: halim kim
>Assignee: halim kim
>Priority: Minor
> Fix For: 5.3.0
>
> Attachments: OOZIE-3716.patch
>
>
> When you execute oozie java action, there is no message like below if
> LauncherSecurityManager throws an exceptions.
> {code:java}
> <<< Invoc
[jira] [Updated] (OOZIE-3716) Invocation of Main class completed Message is skipped when LauncherSecurityManager calls system exit
[
https://issues.apache.org/jira/browse/OOZIE-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
halim kim updated OOZIE-3716:
-
Fix Version/s: 5.3.0
> Invocation of Main class completed Message is skipped when
> LauncherSecurityManager calls system exit
>
>
> Key: OOZIE-3716
> URL: https://issues.apache.org/jira/browse/OOZIE-3716
> Project: Oozie
> Issue Type: Wish
> Components: action
>Affects Versions: 5.0.0, 5.1.0, 5.2.0, 5.3.0, 5.2.1
>Reporter: halim kim
>Assignee: halim kim
>Priority: Minor
> Fix For: 5.3.0
>
> Attachments: OOZIE-3716.patch
>
>
> When you execute oozie java action, there is no message like below if
> LauncherSecurityManager throws an exceptions.
> {code:java}
> <<< Invocation of Main class completed <<<
> {code}
> However, if system exit code from LauncherSecurityManager is zero, it is
> possible to consider main() method finished successfully.
> Therefore, there is no problem with printing "*<<< Invocation of Main class
> completed <<<*" message in such cases.
> Oozie 4.x version prints the message in finally block but Oozie 5.x version
> does not(There is Transition from LauncherMapper to LauncherAM class in oozie
> 5.x version.)
> https://github.com/apache/oozie/blob/3d0843260199799be634dc330d98f1362536fcd5/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMapper.java#L232-L272
> This issue feels trivial but can cause a problem in hue editor.
> hue uses regular expression to distinguish whether oozie java action is
> successfull or not.
> https://github.com/cloudera/hue/blob/c0443438e9a29b9fbf22566022aeef27fc4c606b/desktop/libs/notebook/src/notebook/connectors/oozie_batch.py#L54
> The regular expression does not match if there is no "<<< Invocation of Main
> class completed <<<" message so that hue considers oozie java action is not
> completed even though main method of oozie java action is successful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3716) Invocation of Main class completed Message is skipped when LauncherSecurityManager calls system exit
[
https://issues.apache.org/jira/browse/OOZIE-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713810#comment-17713810
]
Hadoop QA commented on OOZIE-3716:
--
PreCommit-OOZIE-Build started
> Invocation of Main class completed Message is skipped when
> LauncherSecurityManager calls system exit
>
>
> Key: OOZIE-3716
> URL: https://issues.apache.org/jira/browse/OOZIE-3716
> Project: Oozie
> Issue Type: Wish
> Components: action
>Affects Versions: 5.0.0, 5.1.0, 5.2.0, 5.3.0, 5.2.1
>Reporter: halim kim
>Assignee: halim kim
>Priority: Minor
> Attachments: OOZIE-3716.patch
>
>
> When you execute oozie java action, there is no message like below if
> LauncherSecurityManager throws an exceptions.
> {code:java}
> <<< Invocation of Main class completed <<<
> {code}
> However, if system exit code from LauncherSecurityManager is zero, it is
> possible to consider main() method finished successfully.
> Therefore, there is no problem with printing "*<<< Invocation of Main class
> completed <<<*" message in such cases.
> Oozie 4.x version prints the message in finally block but Oozie 5.x version
> does not(There is Transition from LauncherMapper to LauncherAM class in oozie
> 5.x version.)
> https://github.com/apache/oozie/blob/3d0843260199799be634dc330d98f1362536fcd5/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMapper.java#L232-L272
> This issue feels trivial but can cause a problem in hue editor.
> hue uses regular expression to distinguish whether oozie java action is
> successfull or not.
> https://github.com/cloudera/hue/blob/c0443438e9a29b9fbf22566022aeef27fc4c606b/desktop/libs/notebook/src/notebook/connectors/oozie_batch.py#L54
> The regular expression does not match if there is no "<<< Invocation of Main
> class completed <<<" message so that hue considers oozie java action is not
> completed even though main method of oozie java action is successful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3716) Invocation of Main class completed Message is skipped when LauncherSecurityManager calls system exit
[
https://issues.apache.org/jira/browse/OOZIE-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713808#comment-17713808
]
halim kim commented on OOZIE-3716:
--
[~dionusos]
Here is my example workflow(it is created by apache hue). I utilize simple
hadoop wordcount jar file.
wordcount example counts the number of each word in the files of input
directory and prints results in the output directory.
{code:xml}
Action failed, error
message[${wf:errorMessage(wf:lastErrorNode())}]
${jobTracker}
${nameNode}
org.myorg.WordCount
hdfs://test/input
hdfs://test/output
{code}
and here is the result of oozie job. You can see 'Intercepting System.exit(0)'
message but wordcount job was successful and i was able to find result of
wordcount job in the output directory.
{code:java}
>>> Invoking Main class now >>>
Launcher class: class org.apache.oozie.action.hadoop.JavaMain
INFO: loading log4j config file log4j.properties.
INFO: log4j config file log4j.properties loaded successfully.
{"properties":[{"key":"oozie.launcher.job.id","value":"021-230413183451249-oozie-oozi-W","isFinal":false,"resource":"programmatically"},{"key":"oozie.job.id","value":"021-230413183451249-oozie-oozi-W","isFinal":false,"resource":"programmatically"},{"key":"oozie.action.id","value":"021-230413183451249-oozie-oozi-W@java-0e67","isFinal":false,"resource":"programmatically"},{"key":"mapreduce.job.tags","value":"oozie-2a471a03ba6f13a3a475472233e0fcf0","isFinal":false,"resource":"programmatically"}]}Setting
[tez.application.tags] tag: oozie-2a471a03ba6f13a3a475472233e0fcf0
Setting [spark.yarn.tags] tag: oozie-2a471a03ba6f13a3a475472233e0fcf0
Fetching child yarn jobs
tag id : oozie-2a471a03ba6f13a3a475472233e0fcf0
No child applications found
Java action main class: org.myorg.WordCount
Java action arguments :
hdfs://test/input
hdfs://test/output
Intercepting System.exit(0)
Oozie Launcher, uploading action data to HDFS sequence file:
hdfs://test/oozie-oozi/021-230413183451249-oozie-oozi-W/java-0e67--java/action-data.seq
Stopping AM
Callback notification attempts left 0
Callback notification trying
http://:11000/oozie/callback?id=021-230413183451249-oozie-oozi-W@java-0e67&status=SUCCEEDED
Callback notification to
http://:11000/oozie/callback?id=021-230413183451249-oozie-oozi-W@java-0e67&status=SUCCEEDED
succeeded
Callback notification succeeded
{code}
> Invocation of Main class completed Message is skipped when
> LauncherSecurityManager calls system exit
>
>
> Key: OOZIE-3716
> URL: https://issues.apache.org/jira/browse/OOZIE-3716
> Project: Oozie
> Issue Type: Wish
> Components: action
>Affects Versions: 5.0.0, 5.1.0, 5.2.0, 5.3.0, 5.2.1
>Reporter: halim kim
>Assignee: halim kim
>Priority: Minor
>
> When you execute oozie java action, there is no message like below if
> LauncherSecurityManager throws an exceptions.
> {code:java}
> <<< Invocation of Main class completed <<<
> {code}
> However, if system exit code from LauncherSecurityManager is zero, it is
> possible to consider main() method finished successfully.
> Therefore, there is no problem with printing "*<<< Invocation of Main class
> completed <<<*" message in such cases.
> Oozie 4.x version prints the message in finally block but Oozie 5.x version
> does not(There is Transition from LauncherMapper to LauncherAM class in oozie
> 5.x version.)
> https://github.com/apache/oozie/blob/3d0843260199799be634dc330d98f1362536fcd5/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMapper.java#L232-L272
> This issue feels trivial but can cause a problem in hue editor.
> hue uses regular expression to distinguish whether oozie java action is
> successfull or not.
> https://github.com/cloudera/hue/blob/c0443438e9a29b9fbf22566022aeef27fc4c606b/desktop/libs/notebook/src/notebook/connectors/oozie_batch.py#L54
> The regular expression does not match if there is no "<<< Invocation of Main
> class completed <<<" message so that hue considers oozie java action is not
> completed even though main method of oozie java action is successful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [oozie] dependabot[bot] closed pull request #80: Bump jetty-server from 9.4.44.v20210927 to 10.0.10
dependabot[bot] closed pull request #80: Bump jetty-server from 9.4.44.v20210927 to 10.0.10 URL: https://github.com/apache/oozie/pull/80 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@oozie.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [oozie] dependabot[bot] commented on pull request #80: Bump jetty-server from 9.4.44.v20210927 to 10.0.10
dependabot[bot] commented on PR #80: URL: https://github.com/apache/oozie/pull/80#issuecomment-1513881637 Superseded by #89. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@oozie.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [oozie] dependabot[bot] opened a new pull request, #89: Bump jetty-server from 9.4.44.v20210927 to 10.0.14
dependabot[bot] opened a new pull request, #89: URL: https://github.com/apache/oozie/pull/89 Bumps [jetty-server](https://github.com/eclipse/jetty.project) from 9.4.44.v20210927 to 10.0.14. Release notes Sourced from https://github.com/eclipse/jetty.project/releases";>jetty-server's releases. 10.0.14 Special Thanks to the following Eclipse Jetty community members https://github.com/pzygielo";>@pzygielo (Piotrek Żygieło) https://github.com/jluehe";>@jluehe (jluehe) https://github.com/dzoech";>@dzoech (Dominik Zöchbauer) Changelog https://redirect.github.com/eclipse/jetty.project/issues/9344";>#9344 - Cleanup Multipart handling for CVE-2023-26048 https://redirect.github.com/eclipse/jetty.project/issues/9343";>#9343 - URI Host Mismatch with optional Compliance modes https://redirect.github.com/eclipse/jetty.project/issues/9339";>#9339 - Cleanup Cookie Cutter handling for CVE-2023-26049 https://redirect.github.com/eclipse/jetty.project/issues/9337";>#9337 - LowResourceMonitor.getReasons should include detailed reason instead of hard-coded message (https://github.com/jluehe";>@jluehe) https://redirect.github.com/eclipse/jetty.project/issues/9334";>#9334 - Better support for Cookie RFC 2965 compliance https://redirect.github.com/eclipse/jetty.project/issues/9285";>#9285 - ContextHandler sends redirect on BaseResponse instead of Wrapped Response object from Handler chain https://redirect.github.com/eclipse/jetty.project/issues/9283";>#9283 - Configurable Unsafe Host Header Behaviors https://redirect.github.com/eclipse/jetty.project/issues/9188";>#9188 - Log as info exceptions from server after sending stop with StopMojo. https://redirect.github.com/eclipse/jetty.project/issues/9183";>#9183 - ConnectHandler may close the connection instead of sending 200 OK https://redirect.github.com/eclipse/jetty.project/issues/9128";>#9128 - Do not execute any phase for maven plugin :start (https://github.com/pzygielo";>@pzygielo) https://redirect.github.com/eclipse/jetty.project/issues/9119";>#9119 - Wrong value of javax.servlet.forward.context_path attribute https://redirect.github.com/eclipse/jetty.project/issues/9092";>#9092 - Use ASM Bom https://redirect.github.com/eclipse/jetty.project/issues/9059";>#9059 - IteratingCallback not serializing close() and failed() https://redirect.github.com/eclipse/jetty.project/issues/9055";>#9055 - PathMappings optimizations https://redirect.github.com/eclipse/jetty.project/issues/7650";>#7650 - QueuedThreadPool: Stopped without executing or closing null (https://github.com/dzoech";>@dzoech) Dependencies https://redirect.github.com/eclipse/jetty.project/issues/9242";>#9242 - Bump infinispan-bom to 11.0.17.Final https://redirect.github.com/eclipse/jetty.project/issues/9359";>#9359 - Bump maven.version to 3.9.0 https://redirect.github.com/eclipse/jetty.project/issues/9102";>#9102 - Bump org.apache.aries.spifly.dynamic.bundle to 1.3.6 https://redirect.github.com/eclipse/jetty.project/issues/9098";>#9098 - Bump org.eclipse.osgi to 3.18.200 https://redirect.github.com/eclipse/jetty.project/issues/9106";>#9106 - Bump org.eclipse.osgi.services to 3.11.100 https://redirect.github.com/eclipse/jetty.project/issues/9097";>#9097 - Bump protostream to 4.6.0.Final https://redirect.github.com/eclipse/jetty.project/issues/9367";>#9367 - Bump tycho-p2-repository-plugin to 3.0.2 10.0.13 Special Thanks to the following Eclipse Jetty community members https://github.com/janvojt";>@janvojt (Jan Vojt) https://github.com/joschi";>@joschi (Jochen Schalanda) https://github.com/leonchen83";>@leonchen83 (Baoyi Chen) https://github.com/cowwoc";>@cowwoc (Gili Tzabari) https://github.com/Vlatombe";>@Vlatombe (Vincent Latombe) Changelog https://redirect.github.com/eclipse/jetty.project/issues/9006";>#9006 - WebSocket Message InputStream read() returns signed byte https://redirect.github.com/eclipse/jetty.project/issues/8913";>#8913 - Review Jetty XML syntax to allow calling JDK methods ... (truncated) Commits https://github.com/eclipse/jetty.project/commit/976721d0f3e903a243584d47870ad2f2c1bf9e55";>976721d Updating to version 10.0.14 https://github.com/eclipse/jetty.project/commit/b7075161d015ddce23fbf3db873d5f6b539f6a6b";>b707516 Fix osgi dependencies for update to org.eclipse.osgi.services. https://github.com/eclipse/jetty.project/commit/4d146412c8feac05c25d171b15c4f6ab4d42719b";>4d14641 Fix https://redirect.github.com/eclipse/jetty.project/issues/9334";>#9334 Cookie Compliance (https://redirect.github.com/eclipse/jetty.project/issues/9402";>#9402) https://github.com/eclipse/jetty.project/commit/f01d53895f8930e1ebc52c9d89944df14fe5d6f2";>f01d538 Merge pull request https://redirect.github.com/eclipse/jetty.project/issues/9380";>#9380 from eclipse/dependab
[jira] [Assigned] (OOZIE-3716) Invocation of Main class completed Message is skipped when LauncherSecurityManager calls system exit
[
https://issues.apache.org/jira/browse/OOZIE-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dénes Bodó reassigned OOZIE-3716:
-
Assignee: halim kim
> Invocation of Main class completed Message is skipped when
> LauncherSecurityManager calls system exit
>
>
> Key: OOZIE-3716
> URL: https://issues.apache.org/jira/browse/OOZIE-3716
> Project: Oozie
> Issue Type: Wish
> Components: action
>Affects Versions: 5.0.0, 5.1.0, 5.2.0, 5.3.0, 5.2.1
>Reporter: halim kim
>Assignee: halim kim
>Priority: Minor
>
> When you execute oozie java action, there is no message like below if
> LauncherSecurityManager throws an exceptions.
> {code:java}
> <<< Invocation of Main class completed <<<
> {code}
> However, if system exit code from LauncherSecurityManager is zero, it is
> possible to consider main() method finished successfully.
> Therefore, there is no problem with printing "*<<< Invocation of Main class
> completed <<<*" message in such cases.
> Oozie 4.x version prints the message in finally block but Oozie 5.x version
> does not(There is Transition from LauncherMapper to LauncherAM class in oozie
> 5.x version.)
> https://github.com/apache/oozie/blob/3d0843260199799be634dc330d98f1362536fcd5/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMapper.java#L232-L272
> This issue feels trivial but can cause a problem in hue editor.
> hue uses regular expression to distinguish whether oozie java action is
> successfull or not.
> https://github.com/cloudera/hue/blob/c0443438e9a29b9fbf22566022aeef27fc4c606b/desktop/libs/notebook/src/notebook/connectors/oozie_batch.py#L54
> The regular expression does not match if there is no "<<< Invocation of Main
> class completed <<<" message so that hue considers oozie java action is not
> completed even though main method of oozie java action is successful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3715) Fix fork out more than one transitions submit , one transition submit fail can't execute KillXCommand
[
https://issues.apache.org/jira/browse/OOZIE-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713569#comment-17713569
]
Dénes Bodó commented on OOZIE-3715:
---
[~jmakai] have you had a chance to test this change? Thanks
> Fix fork out more than one transitions submit , one transition submit fail
> can't execute KillXCommand
> -
>
> Key: OOZIE-3715
> URL: https://issues.apache.org/jira/browse/OOZIE-3715
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 5.2.1
>Reporter: chenhaodan
>Assignee: chenhaodan
>Priority: Major
> Labels: patch
> Fix For: trunk
>
> Attachments: OOZIE-3715-001.patch, OOZIE-3715-002.patch,
> OOZIE-3715-003.patch, OOZIE-3715-004.patch, forkSubmitFail_issue.txt,
> status.png
>
>
> When I fork 2 transitions( A and B) to submit , when A transition failed , B
> transition still Running , because can't execute KillXCommand.
> SignalXCommand.startForkedActions, when one transition submit fail will
> create a new ActionStartXCommand and invoke failJob, failJob will add
> WorkflowNotificationXCommand and KillXCommand to
> {color:#ff}*commandQueue*{color} , and callback at XCommand.call method ,
> but we add WorkflowNotificationXCommand and KillXCommand to
> ActionStartXCommand‘s {color:#ff}*commandQueue*{color} , but not
> SignalXCommand , so can't execute KillXCommand.
> The code is as follows :
>
> {code:java}
> public void startForkedActions(List
> workflowActionBeanListForForked) throws CommandException {
> ..
> for (Future result : futures) {
> ..
> if (context.getJobStatus() != null &&
> context.getJobStatus().equals(Job.Status.FAILED)) {
> new ActionStartXCommand(context.getAction().getId(),
> null).failJob(context);
> ..
> }
>..
> }
> {code}
>
> {code:java}
> public void failJob(ActionExecutor.Context context, WorkflowActionBean
> action) throws CommandException {
> WorkflowJobBean workflow = (WorkflowJobBean) context.getWorkflow();
> if (!handleUserRetry(context, action)) {
> incrActionErrorCounter(action.getType(), "failed", 1);
> LOG.warn("Failing Job due to failed action [{0}]",
> action.getName());
> try {
> workflow.getWorkflowInstance().fail(action.getName());
> WorkflowInstance wfInstance = workflow.getWorkflowInstance();
> ((LiteWorkflowInstance)
> wfInstance).setStatus(WorkflowInstance.Status.FAILED);
> workflow.setWorkflowInstance(wfInstance);
> workflow.setStatus(WorkflowJob.Status.FAILED);
> action.setStatus(WorkflowAction.Status.FAILED);
> action.resetPending();
> queue(new WorkflowNotificationXCommand(workflow, action));
> queue(new KillXCommand(workflow.getId()));
> InstrumentUtils.incrJobCounter(INSTR_FAILED_JOBS_COUNTER_NAME, 1,
> getInstrumentation());
> }
> catch (WorkflowException ex) {
> throw new CommandException(ex);
> }
> }
> }
> {code}
>
> {code:java}
> public final T call() throws CommandException {
> if (commandQueue != null) {
> for (Map.Entry>> entry :
> commandQueue.entrySet()) {
> LOG.debug("Queuing [{0}] commands with delay [{1}]ms",
> entry.getValue().size(), entry.getKey());
> if (!callableQueueService.queueSerial(entry.getValue(),
> entry.getKey())) {
> LOG.warn("Could not queue [{0}] commands with delay [{1}]ms,
> queue full", entry.getValue()
> .size(), entry.getKey());
> }
> }
> }
> }
> {code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (OOZIE-3716) Invocation of Main class completed Message is skipped when LauncherSecurityManager calls system exit
[
https://issues.apache.org/jira/browse/OOZIE-3716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17713568#comment-17713568
]
Dénes Bodó commented on OOZIE-3716:
---
[~khr9603]
Thanks for the change. Can you please share an example how the situation can
occur? I see that {{actionMainExecutedProperly}} can be true if the {{cause
instanceof SecurityException}} .
Also can you please upload the diff file to the Jira and push the "Submit
Patch" button?
Thanks
Denes
> Invocation of Main class completed Message is skipped when
> LauncherSecurityManager calls system exit
>
>
> Key: OOZIE-3716
> URL: https://issues.apache.org/jira/browse/OOZIE-3716
> Project: Oozie
> Issue Type: Wish
> Components: action
>Affects Versions: 5.0.0, 5.1.0, 5.2.0, 5.3.0, 5.2.1
>Reporter: halim kim
>Priority: Minor
>
> When you execute oozie java action, there is no message like below if
> LauncherSecurityManager throws an exceptions.
> {code:java}
> <<< Invocation of Main class completed <<<
> {code}
> However, if system exit code from LauncherSecurityManager is zero, it is
> possible to consider main() method finished successfully.
> Therefore, there is no problem with printing "*<<< Invocation of Main class
> completed <<<*" message in such cases.
> Oozie 4.x version prints the message in finally block but Oozie 5.x version
> does not(There is Transition from LauncherMapper to LauncherAM class in oozie
> 5.x version.)
> https://github.com/apache/oozie/blob/3d0843260199799be634dc330d98f1362536fcd5/sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherMapper.java#L232-L272
> This issue feels trivial but can cause a problem in hue editor.
> hue uses regular expression to distinguish whether oozie java action is
> successfull or not.
> https://github.com/cloudera/hue/blob/c0443438e9a29b9fbf22566022aeef27fc4c606b/desktop/libs/notebook/src/notebook/connectors/oozie_batch.py#L54
> The regular expression does not match if there is no "<<< Invocation of Main
> class completed <<<" message so that hue considers oozie java action is not
> completed even though main method of oozie java action is successful.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
