Red Hat Bugzilla – Bug 1279821
Synchronization of a deployment unit between EJB services app and Business Central fails
Last modified: 2015-12-03 07:18:07 EST
Created attachment 1092166 [details]
exception stacktrace from a server log
Description of problem:
Having Business Central deployed together with EJB services application, synchronization of deployment units between Business Central and EJB app fails due to a failure in EJB lookup.
The EJB lookup is unsuccessful, because EJB app. created an async. work item handler which uses EJB executor to accomplish it's task. However, when the handler gets executed by Business Central, this issue shows, as there is not such EJB in Business Central.
Version-Release number of selected component (if applicable):
often, but not every time
Steps to Reproduce:
1. deploy Business Central and EJB services app to EAP 6.4.4.GA
2. trigger deploy operation via EJB remoting
3. watch for an exception in a server log
Please find an example of EJB service app here .
problem is caused by additional work item handler registration via deployment descriptor for ejb app to register async work item handlers. Since it is then stored as part of job description so it can be replicated to all server instances working with same db the special work item handler should not be saved. It is anyway registered always when deploying via ejb services so no need to persist it.
The issue persists in 6.2.0.CR1
pull request created to fix the issue https://github.com/droolsjbpm/jbpm/pull/345
merged pull request that added missing bits for ejb deployment service
Verified with BPMS-6.2.0.CR2