The Management CLI session is closed when it is detected it is a session opened from the same server installation that is going to be updated/reverted. This is done to prevent lock issues in Windows when jboss-modules.jar is being updated from the candidate server at the apply server phase.

Right now, there is no synchronization between Management CLI close and when the candidate server is being applied, but generally this should occur before the server is completely shutdown.

However, there are chances this can occur. A simple approach could be to force and delay the apply server phase enough time to assume that the client session has been closed. However, even delaying it there is no guarantee that this cannot occur, since anyone can open any Management CLI session or even have more management sessions opened at the same time, it would also increase the server downtime, although additional seconds can be perfectly assumable.

There are multiple options, but probably delay the server until all the Management CLI clients running from its own installation are closed would be the most reliable approach. If not all the Management CLI sessions are closed, then restart without applying the candidate server.