[jboss-jira] [JBoss JIRA] (WFCORE-199) Domain graceful shutdown may attempt to use an AbstractMessageHandler that is shutdown
Brian Stansberry (JIRA)
issues at jboss.org
Thu Oct 23 17:12:35 EDT 2014
Brian Stansberry created WFCORE-199:
---------------------------------------
Summary: Domain graceful shutdown may attempt to use an AbstractMessageHandler that is shutdown
Key: WFCORE-199
URL: https://issues.jboss.org/browse/WFCORE-199
Project: WildFly Core
Issue Type: Bug
Components: Domain Management
Affects Versions: 1.0.0.Alpha10
Reporter: Brian Stansberry
ManagedServer during shutdown tries to send a "shutdown" op to the remote server, triggering a graceful suspend.
Problem is, the TransactionalProtocolClient it uses is using a ManagementChannelHandler that may have been shut down. The service that controls the lifecycle of the ManagementChannelHandler (i.e. ManagementChannelOpenListenerService) is written to ensure that it isn't shutdown open until incoming requests complete, but there is nothing preventing shutdown when client uses are desired.
The specific area where this can be a problem is the assert !shutdown at
https://github.com/wildfly/wildfly-core/blob/master/protocol/src/main/java/org/jboss/as/protocol/mgmt/ActiveOperationSupport.java#L151
One possible solution is to distinguish locally initiated active operations from remote ones. AIUI the goal is to reject further remote ones.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
More information about the jboss-jira
mailing list