1 Reply Latest reply on Mar 18, 2019 2:03 AM by jaikiran

    Deployment hang upgrading from EAP 6.4.9 to 6.4.10


      There seems to be some changes implemented in JBoss EAP 6.4.10 that is causing deployment of our app to hang during startup.




      "ServerService Thread Pool -- 50" #112 prio=5 os_prio=0 tid=0x000000001edd0800 nid=0x204c in Object.wait() [0x0000000025c5d000]

        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.jboss.as.ee.component.BasicComponent.waitForComponentStart(BasicComponent.java:117)

             *- locked <0x00000000c56881e0> (a org.jboss.as.ejb3.component.stateless.StatelessSessionComponent)*




      I've been able to pinpoint to JPA changes made between 6.4.9 and 6.4.10 as I can drop in JPA jars directly into 6.4.10 and don't get this issue.


      I believe associated to: WFLY-6441 Setup the Java EE namespace on persistence unit start by scottmarlow · Pull Request #8810 · wildfly/wildfly · …


      Any thoughts?

        • 1. Re: Deployment hang upgrading from EAP 6.4.9 to 6.4.10

          Hello Daniel,


          If you have a JBoss EAP support contract, please raise this as a support ticket in the support portal. That way, it's easier to provide any patch that might be needed for this.


          If you don't have access to the support portal, then you can raise this as an issue in WildFly (the upstream project) if it's still reproducible in latest released WildFly versions.