[
https://issues.jboss.org/browse/WFLY-11978?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFLY-11978:
-----------------------------------------
[~dlmiles] If you can do a couple things when this happens and attach the output, it may
help in diagnosis:
1) Take a thread dump of the server process.
2) Open a terminal window, start a CLI and connect it to the server and execute:
/core-service=service-container:dump-services > svcdump.txt
That will dump the status of the various services into a file in the working dir.
EAR with 2+ JPA does not shutdown cleanly
-----------------------------------------
Key: WFLY-11978
URL:
https://issues.jboss.org/browse/WFLY-11978
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 16.0.0.Final
Environment: Windows JDK8 WF16
Reporter: Darryl Miles
Assignee: Scott Marlow
Priority: Major
EAR with 2+ JPA does not shutdown cleanly.
I see in the logs each JPA project have an entry:
WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service
'blah....jpa.project1'
WFLYJPA0011: Stopping Persistence Unit (phase 2 of 2) Service
'blah....jpa.project2'
then a few lines later:
WFLYJPA0011: Stopping Persistence Unit (phase 1 of 2) Service
'blah....jpa.project2'
I never see the "phase 1 of 2" entry for "jpa.project1" in the log.
The container will wait 300 seconds and timeout.
The management console during the time shows
Operation: undeploy
Execution Status: awaiting-stablility.
The container is killed and the configuration.xml still contains the EAR deployment info,
as undeploy did not complete.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)