Uploaded image for project: 'WildFly Core'
  1. WildFly Core
  2. WFCORE-199

Domain graceful shutdown may attempt to use an AbstractMessageHandler that is shutdown

    Details

    • Type: Bug
    • Status: Reopened (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0.0.Alpha10
    • Fix Version/s: None
    • Component/s: Management
    • Labels:

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  brian.stansberry Brian Stansberry
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated: