[
https://issues.apache.org/jira/browse/CAMEL-9449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117552#comment-15117552
]
ASF GitHub Bot commented on CAMEL-9449:
---------------------------------------
GitHub user lburgazzoli opened a pull request:
https://github.com/apache/camel/pull/806
CAMEL-9449 - Allow to specify custom exit code when camel exits due t…
…o expired Duration
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/lburgazzoli/apache-camel CAMEL-9449
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/806.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #806
----
commit 40264077412c5971b394f15bcd399dfc6e80105e
Author: lburgazzoli <[email protected]>
Date: 2016-01-26T16:52:58Z
CAMEL-9449 - Allow to specify custom exit code when camel exits due to
expired Duration
----
> Allow to specify custom exit code when camel exits due to expired Duration
> --------------------------------------------------------------------------
>
> Key: CAMEL-9449
> URL: https://issues.apache.org/jira/browse/CAMEL-9449
> Project: Camel
> Issue Type: New Feature
> Components: camel-core
> Reporter: Nishant Jaiswal
> Assignee: Luca Burgazzoli
> Priority: Minor
>
> When java main class exits where duration is expired then it should be
> allowed to exit with a different exit code than 0.
> Currently when java main class exists after setDuration() is set to say 60
> seconds, it always does that with exit code 0
> This does not give flexibility to the parent process to know if camel process
> exited because it was successful or because Duration limit was it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
