Details
-
Bug
-
Resolution: Done
-
Major
-
JDG 7.0.0 DR2
-
None
Description
When I use wildfly-maven-plugin in our tests to start/stop JDG server, and the plugin running the tests (maven-failsafe-plugin) fails, the JDG server hangs during shutdown and has to be killed manually. If the failsafe plugin finishes without problems, the server stops correctly.
I've created a simple reproducer for the issue (attached pom.xml), run it like this:
mvn clean verify -Djdg.home=<path-to-unzipped-dr2-server> -Dit.test=nonExistingTest
Running it without the parameter -Dit.test=nonExistingTest, the failsafe plugin doesn't fail and the server shutdowns correctly.
Attached is the stacktrace of the hanging JDG and server trace log.
From the stacktrace it looks like the server is stuck in org.jboss.as.server.BootstrapImpl$ShutdownHook.shutdown, which registers a callback to ServiceContainerImpl which should be called when all the services terminate (controlled by org.jboss.msc.service.MultipleRemoveListener), but it isn't called, because some services do not end. FWIW, I tracked down which those are:
jboss.as
jboss.as.external-module-service
jboss.as.server-controller
jboss.as.server-executor
jboss.as.service-module-loader
jboss.content-repository
jboss.deployment-mount-provider
jboss.path.manager
jboss.remoting.endpoint.management
jboss.serverManagement.controller.management.worker
I have no idea how any of this should be related to the failsafe plugin failing, though.
Attachments
Issue Links
- relates to
-
ISPN-6476 Integration test modules shouldn't change the failsafe plugin's lifecycle
- Closed