Issue

We do some parameter verification during JBOSS EAP start up, if the verification fails, application will shutdown JBOSS EAP instance.
In EAP 6.0.1, this works. However, in EAP 6.2.1, it seems that JBOSS EAP instance cannot stop successfully, it will hang up there instead. Here comes the stack:

    ServerService Thread Pool -- 48" prio=10 tid=0x00007f299819c000 nid=0x2e27 waiting on condition [0x00007f299cf34000]
      java.lang.Thread.State: WAITING (parking)
        at sun.misc.Unsafe.park(Native Method)
        - parking to wait for  <0x000000072aea9770> (a org.jboss.as.controller.ModelControllerLock$Sync)
        ...
        at org.jboss.as.controller.OperationContextImpl.acquireControllerLock(OperationContextImpl.java:713)
        at org.jboss.as.server.operations.ServerShutdownHandler.execute(ServerShutdownHandler.java:69)
        ...
        at org.jboss.as.jmx.PluggableMBeanServerImpl.invoke(PluggableMBeanServerImpl.java:731)
        at com.test.ShutdownJbossDuringStartupImpl.shutdownJboss(ShutdownJbossDuringStartupImpl.java:50)
        ...

We’d like to know:
1. What’s the root cause for JBOSS EAP hang?
2. Has JBOSS changed its implementation? In previous version, current solution works well.
3. Is there any best practice for stopping JBOSS EAP during app start up?
4. Is there any workaround?