Bug 1011514
| Summary: | session-migration: signal in subprocess ignored. | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Marek Baluch <mbaluch> | ||||||
| Component: | jBPM Core | Assignee: | Maciej Swiderski <mswiders> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Marek Baluch <mbaluch> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.0.0 | CC: | mrietvel | ||||||
| Target Milestone: | ER5 | ||||||||
| Target Release: | 6.0.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-08-06 20:12:52 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Created attachment 802215 [details]
child (sub) process
fixed by ensuring it does use same column name in EventTypes table master: https://github.com/droolsjbpm/jbpm/commit/fbdfd3535d1a820848b8300a81e70532e7c445c3 6.0.x https://github.com/droolsjbpm/jbpm/commit/bf07a9f468445f80527459b8e2ff24b74aee9411 Verified on ER5. Just double checking: has this been verified on all supported databases? |
Created attachment 802214 [details] parent process Description of problem: When a signal is expected in a subprocess it is ignored. How to reproduce: (using the attached processes) 1) start a process in jbpm5 2) signal it ("Continue" signal) in jbpm6. Expected result: Both process instances (parent and child) will be COMPLETED Actual results: Both process instances are in ACTIVE state Note: I found that when I access the process instances before the signal is made all is fine KieSession ksession = restoreKnowledgeSession(sinfo.getSessionId(), "BPMN2-CallActivity.bpmn2", "BPMN2-CallActivitySubProcess.bpmn2"); for (Long pid : sinfo.getProcessInstanceIds()) { System.out.println("Instance: " + pid + ", State: " + ksession.getProcessInstance(pid)); } ksession.signalEvent("Continue", null); ksession.dispose();