[jboss-jira] [JBoss JIRA] Resolved: (JBBOOT-20) Bootstrap server relies on JVM lifecycle to shutdown the server

[Andrew Lee Rubinger (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBBOOT-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Lee Rubinger resolved JBBOOT-20.
---------------------------------------

    Resolution: Won't Fix


The newer impls have no notion of JVM lifecycle.  It's up to the caller to implement these.

Resolving as "won't fix" in the legacy, and it won't be present in the new impl.

> Bootstrap server relies on JVM lifecycle to shutdown the server
> ---------------------------------------------------------------
>
>                 Key: JBBOOT-20
>                 URL: https://jira.jboss.org/jira/browse/JBBOOT-20
>             Project: JBoss Bootstrap
>          Issue Type: Bug
>    Affects Versions: 1.0.0-Beta-2
>            Reporter: jaikiran pai
>            Assignee: Andrew Lee Rubinger
>
> Bootstrap server internally uses a runtime ShutdownHook which relies on a system property (defaulted to true) "jboss.shutdown.forceHalt". The shutdown hook then halts the VM with a default error code = 0 (=SUCCESS). Currently this affects the testcases which use bootstrap to start the server. Even if these tests fail, because of the shutdown hook, the JVM process exit code is always 0 (=SUCCESS). unless, the following 2 properties are set to "false" in the testcase:
> ...
> props.put(ServerConfig.EXIT_ON_SHUTDOWN, "false");
> System.setProperty("jboss.shutdown.forceHalt", "false");
> ...
> server.init(props); 
> Build tools like Maven rely on the JVM process return code to decide whether the tests have succeeded to carry on with the rest of the build process steps.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira