JMX notification not sent until after shutdown is complete
----------------------------------------------------------
Key: JBBOOT-105
URL:
https://jira.jboss.org/jira/browse/JBBOOT-105
Project: JBoss Bootstrap
Issue Type: Bug
Components: impl-base
Affects Versions: impl-base-2.0.0-alpha-3
Reporter: Paul Ferraro
Assignee: Andrew Lee Rubinger
In bootstrap 1.0.x, and in the legacy implementation, the org.jboss.system.server.stopped
JMX notification was sent prior to the shutdown of the server. The AS TomcatService
relies on this mechanism to stop its http/ajp connectors before stopping the service,
along with any deployed web applications.
In 2.0.0-alpha-3, however, this notification is not sent until after shutdown is complete.
Consequently, the http/ajp connectors are not getting stopped until after all web
applications are undeployed. It is now possible for a web request to reach the connectors
before they are stopped, but after the requested web application was already undeployed,
causing a 404 (page not found) error.
--
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