[ https://issues.jboss.org/browse/WFLY-9516?page=com.atlassian.jira.plugin.... ] Scott Marlow edited comment on WFLY-9516 at 11/15/17 3:41 PM: -------------------------------------------------------------- [~bmaxwell] to ensure that the persistence unit is available to the started EJBs, during application deployment, we add an internal service dependency from the EJB component(s) to the persistence unit(s), so the EJB will not start until the persistence unit has started. With persistence units defined in multiple ejb (sub) modules and initialize-in-order=true, we are going to get into trouble as we are only starting one ejb jar module at a time but adding dependencies from the ejb jar module on all of the persistence units defined in other modules. {quote} "jboss.deployment.subunit.\"reproducer-ear-0.1.ear\".\"reproducer-ejb.jar\".component.StatelessBean1.START is missing [jboss.persistenceunit.\"reproducer-ear-0.1.ear/reproducer-ejb2.jar#pu2\"]" {quote} Regarding what is at the top level of the EAR, ejb modules are sub-deployments. A jar with persistence.xml in ear/lib is at the top level of EAR deployment. An application workaround, could be to move the persistence unit definitions to (non-ejb) jars in ear/lib. A (possible) fix could be: * Introduce a persistence unit hint to change our deployment code (JPA/Weld) to not add component dependencies on persistence units contained by other subdeployments. * Or change our deployment code (JPA/WELD) to not add component dependencies on persistence units contained by other subdeployments if the initialize-in-order=true. was (Author: smarlow): [~bmaxwell] to ensure that the persistence unit is available to the started EJBs, during application deployment, we add an internal service dependency from the EJB component(s) to the persistence unit(s), so the EJB will not start until the persistence unit has started. With persistence units defined in multiple ejb (sub) modules and initialize-in-order=true, we are going to get into trouble as we are only starting one ejb jar module at a time but adding dependencies from the ejb jar module on all of the persistence units defined in other modules. {quote} "jboss.deployment.subunit.\"reproducer-ear-0.1.ear\".\"reproducer-ejb.jar\".component.StatelessBean1.START is missing [jboss.persistenceunit.\"reproducer-ear-0.1.ear/reproducer-ejb2.jar#pu2\"]" {quote} Regarding what is at the top level of the EAR, ejb modules are sub-deployments. A jar with persistence.xml in ear/lib is at the top level. An application workaround, could be to move the persistence unit definitions to (non-ejb) jars in ear/lib. A (possible) fix could be: * Introduce a persistence unit hint to change our deployment code (JPA/Weld) to not add component dependencies on persistence units contained by other subdeployments. * Or change our deployment code (JPA/WELD) to not add component dependencies on persistence units contained by other subdeployments if the initialize-in-order=true. -- This message was sent by Atlassian JIRA (v7.5.0#75005)