-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
If I deploy a process application which provokes unsatisfied service dependencies in the INSTALL phase, the MSC runs into a deadlock. The reason is that we depend on the VIEW service of the ProcessApplication component (Singleton EJB) and not also on its START service.
When the org.camunda.bpm.container.impl.jboss.service.ProcessApplicationDeploymentService starts, the VIEW service is installed but the component is not yet started. If we then call the getName() method on the session bean, this call blocks until the START service is up. But it never comes up since there are unsatisfied dependencies. This causes us to block the phase processor and thus constitutes a deadlock.
I fixed it by adding a dependency on the START service.
Integration testcase is added.