Bug 1011514 - session-migration: signal in subprocess ignored.
Summary: session-migration: signal in subprocess ignored.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Core
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER5
: 6.0.0
Assignee: Maciej Swiderski
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-24 12:59 UTC by Marek Baluch
Modified: 2014-08-06 20:12 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:12:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
parent process (2.85 KB, application/xml)
2013-09-24 12:59 UTC, Marek Baluch
no flags Details
child (sub) process (6.66 KB, application/xml)
2013-09-24 13:00 UTC, Marek Baluch
no flags Details

Description Marek Baluch 2013-09-24 12:59:35 UTC
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();

Comment 1 Marek Baluch 2013-09-24 13:00:05 UTC
Created attachment 802215 [details]
child (sub) process

Comment 2 Maciej Swiderski 2013-09-27 11:16:48 UTC
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

Comment 3 Marek Baluch 2013-11-25 11:27:55 UTC
Verified on ER5.

Comment 4 Marco Rietveld 2013-12-12 14:38:26 UTC
Just double checking: has this been verified on all supported databases?


Note You need to log in before you can comment on or make changes to this bug.