[
https://issues.jboss.org/browse/WFLY-3019?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-3019:
----------------------------------------
Anyone who looks at this, search the code for uses of
"jboss.unsupported.fail-boot-on-runtime-failure" which the testsuite uses to
trigger this kind of behavior. Implementing this might just involve exposing a proper
configuration mechanism for this. Having different behavior based on whether the failure
occurred in subsystems or deployments would require something more (and may have
unacceptable boot speed costs; or maybe not.)
Shutdown on startup error
-------------------------
Key: WFLY-3019
URL:
https://issues.jboss.org/browse/WFLY-3019
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 8.0.0.Final
Reporter: Takayoshi Kimura
Currently WildFly starts and up running although it got critical errors during boot.
For example, 8080 port is being used by the other process and undertow subsystem was not
functioning, transaction manager and logging subsystems are failed to boot due to file
permission error, or someone started the instance twice by mistake.
It would be nice if we can have an option to trigger shutdown the non-healthy instance in
these boot error situations, for subsystem level errors and for deployment errors.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira