Created attachment 940769 [details] [0] process definition Description of problem: It is not possible to complete Human Task when - two or more embedded sub processes are modelled within one main process - Human Task is located within this embedded sub process - Java Security Manager is enabled Version-Release number of selected component (if applicable): BPM Suite 6.0.2 BPM Suite 6.0.3 How reproducible: always Steps to Reproduce: 1. Import attached BPMN process into business-central (change task actor accordingly) 2. Start the process, claim the task, complete the task 3. Observe the exception Actual results: It is not possible to complete the task Expected results: It is possible to complete the task
Created attachment 940771 [details] [2] server.log
I don't know why this issue presents itself only when multiple embedded sub processes are used, however, I was able to bypass it with the configuration change of kie.policy file, adding: permission org.jboss.as.naming.JndiPermission "UserTransaction", "lookup"; permission org.jboss.as.naming.JndiPermission "TransactionManager", "lookup"; permission org.jboss.as.naming.JndiPermission "TransactionSynchronizationRegistry", "lookup"; Helped to resolve the issue at my end.
Note: If you want to enable Java Security Manager just install the product using UI installer and tick the checkbox "enable Java Security Manager". I have used these default settings for reproducing the issue.
When I set boundary signal event to CancelActivity = true in the attached process definition, the issues vanishes. However, I am not sure if the PermissionDenied exception was the desired behaviour even if the process definition wasn't entirely correct.
QE: I managed to reproduce the issue using the steps from comment #1 with BPMS 6.0.3. However I was unable to reproduce it with 6.1.0 DR3, because that version (nor the previous version DR2) does not even start using standalone-secure.sh. This has been reported in separate bug #1148755
Since I fixed the related bug 1148755, so please test this issue again on ER1 to make sure this still a problem on 6.1.0.
QE: I checked with BPM Suite 6.1.0 ER2, which can now be started successfully with standalone-secure.sh It seems that the issue is no longer there - I was able to complete both tasks from the process provided, there was no exception. But I'm not sure what that means for 6.0. Rajesh?
Verified with BPM Suite 6.1.0 ER2