Created attachment 902836 [details] server log Description of problem: Projects my-store-brms-kmodule and helloworld-brms-kmodule from jboss-brms-repository cannot be builded and deployed on BPMS business central. See log file in attachment. Version-Release number of selected component (if applicable): BPMS 6.0.2.ER3. How reproducible: Always on BPMS business central. Steps to Reproduce: 1. Clone jboss-brms-repository from quickstarts zip file to BPMS business central. 2. Select project and navigate to Project Editor. 3. Click on Build & Deploy. Actual results: An exception is occurred. Expected results: Project should be builded and deployed without exception. Additional info: Building and deploying projects from jboss-brms-repository works fine on BRMS business central.
Attached server log suggests this is a jBPM Console issue. Reassigning.
I think this issue is no long valid any more. Since I didn't find this issue for 6.1.0. Double Checked with 6.1.0 DR3 too.
Version-Release number of selected component (if applicable): BPMS-6.1.0-DR3 BRMS-6.1.0-DR3 New problem appeared. Building quickstarts repo now doesn't work in both types of business central (BRMS, BPMS). It seems to be same error as in BZ 1145985.
Created attachment 941030 [details] New Server log
I can't reproduce the issue on both DR3 and DR4. It deployed ok when I testing the quickstarts. Could you verify this again on DR4?
Still in DR4.
I have been able to successfully built the projects in BRMS Business Central ER5. However, when building with BPM Suite Business Central, I am getting an exception for helloworld-brms-kmodule and my-store-brms-kmodule: java.lang.IllegalStateException: Cannot find ksession, either it does not exist or there are multiple default ksession in kmodule.xml at org.jbpm.services.cdi.impl.manager.InjectableRegisterableItemsFactory.getWorkItemHandlers(InjectableRegisterableItemsFactory.java:155) [jbpm-services-cdi-6.2.0.Final-redhat-1.jar:6.2.0.Final-redhat-1] The reason seems to be the fact that the kmodules declare only one stateless ksession. No stateful one is defined and the deployment fails because jBPM can't use stateless sessions. When changing the config to stateful, the deployment is successful. We either need to make the default session stateful in the example kmodules, somehow fix/update the behavior when there is no stateful session found.
The default sessions are now stateful. This is quick fix for now. I will review all the kmodules in future and we may decide to fix it another way. https://github.com/jboss-developer/jboss-brms-repository/commit/52a658d437c0f2d5645121204a9d2eaa8c255acd
I was too hasty. The quickstarts rely on the stateless sessions so they need to stay there. I added second ksession (stateful) into the configs. https://github.com/jboss-developer/jboss-brms-repository/commit/815397a99b22cc18d3565d0d715aa5722ee1d74f
Verified on BPMS 6.1.0.ER6.