[
https://issues.apache.org/jira/browse/OOZIE-786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13239858#comment-13239858
]
[email protected] commented on OOZIE-786:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4524/
-----------------------------------------------------------
(Updated 2012-03-27 19:33:00.979060)
Review request for oozie.
Changes
-------
removing spurious imports
Summary
-------
making the webapp listener to do a System.exit(1) if an error occurs while
starting the services.
This addresses bug OOZIE-786.
https://issues.apache.org/jira/browse/OOZIE-786
Diffs (updated)
-----
trunk/core/src/main/java/org/apache/oozie/servlet/ServicesLoader.java 1305822
Diff: https://reviews.apache.org/r/4524/diff
Testing
-------
build/deployed oozie and tested running the oozie-run.sh command without a
created DB, and verified the Tomcat process ends.
Thanks,
Alejandro
> tomcat should stop if oozie does not start correctly
> ----------------------------------------------------
>
> Key: OOZIE-786
> URL: https://issues.apache.org/jira/browse/OOZIE-786
> Project: Oozie
> Issue Type: Improvement
> Components: core
> Affects Versions: 3.2.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Fix For: 3.2.0
>
>
> Currently, if oozie fails to start the embedded tomcat continues running.
> To simplify monitoring and to make oozie-run.sh to fail, the Tomcat server
> should be brought down.
--
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
