[
https://issues.jboss.org/browse/WFLY-11978?page=com.atlassian.jira.plugin...
]
Darryl Miles commented on WFLY-11978:
-------------------------------------
I have @Startup @Singleton that injects 1 @PersistenceContext with a @PostContruct that
does nothing { if(true) return; }
I have added the 2 additional settings:
<property name="hibernate.enhancer.enableDirtyTracking"
value="true"/>
<property name="hibernate.generate_statistics"
value="true"/>
I have added this 1 additional setting (to 1 JPA project only) :
<shared-cache-mode>ENABLE_SELECTIVE</shared-cache-mode>
Interestingly the first one makes the EAR take 20.45 seconds to deploy, instead of 13.36
seconds when false.
This slowdown seems to fix the race as I can get it to shutdown, I assume there is extra
stuff doing on during shutdown as well.
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
Attachments: td8948.txt
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)