[jboss-jira] [JBoss JIRA] (WFLY-11978) EAR with 2+ JPA does not shutdown cleanly

[Darryl Miles (Jira)]

    [ https://issues.jboss.org/browse/WFLY-11978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725766#comment-13725766 ] 

Darryl Miles commented on WFLY-11978:
-------------------------------------

Just to say I have the results from these 2 commands.
I need to work out how to sanitize the output to be able to send  the svcdump.txt but I think I can see the stack track of the problem in thread dump.

See attached thread dump.

"ServerService Thread Pool -- 96" #274 prio=5 os_prio=0 tid=0x000000002e24f800 nid=0x20cc in Object.wait() [0x000000004d89e000]
   java.lang.Thread.State: WAITING (on object monitor)
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(Object.java:502)
        at org.infinispan.factories.AbstractComponentRegistry.stop(AbstractComponentRegistry.java:359)
        - locked <0x00000005c61cee50> (a org.infinispan.factories.InternalCacheFactory$1)
        at org.infinispan.cache.impl.SimpleCacheImpl.stop(SimpleCacheImpl.java:173)
        at org.infinispan.cache.impl.AbstractDelegatingCache.stop(AbstractDelegatingCache.java:520)
        at org.infinispan.cache.impl.AbstractDelegatingCache.stop(AbstractDelegatingCache.java:520)
        at org.infinispan.hibernate.cache.v53.impl.BaseRegionImpl.destroy(BaseRegionImpl.java:74)
        at org.infinispan.hibernate.cache.v53.impl.QueryResultsRegionImpl.destroy(QueryResultsRegionImpl.java:17)
        at org.hibernate.cache.internal.EnabledCaching.close(EnabledCaching.java:546)
        at org.hibernate.internal.SessionFactoryImpl.close(SessionFactoryImpl.java:803)
        at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$2$1.run(PersistenceUnitServiceImpl.java:259)
        - locked <0x000000071a88c298> (a org.jboss.as.jpa.service.PersistenceUnitServiceImpl$2$1)
        at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$2$1.run(PersistenceUnitServiceImpl.java:236)
        at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:649)
        at org.jboss.as.jpa.service.PersistenceUnitServiceImpl$2.run(PersistenceUnitServiceImpl.java:290)
        at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
        at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
        at java.lang.Thread.run(Thread.java:748)
        at org.jboss.threads.JBossThread.run(JBossThread.java:485)




I say it is when 2 JPAs are in the EAR as when I remove one from the project EAR build and comment out @PersistenceContext usage to make it start up.  I can shutdown Wildfly ok with either JPA running individually.


> 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)