Bug 1072463

Summary:

Events are not signalled to process

Product:

[Retired] JBoss BPMS Platform 6

Reporter:

Marek Winkler <mwinkler>

Component:

jBPM Core

Assignee:

Maciej Swiderski <mswiders>

Status:

CLOSED CURRENTRELEASE

QA Contact:

Ivo Bek <ibek>

Severity:

medium

Docs Contact:

Priority:

high

Version:

6.0.1

CC:

etirelli, kverlaen, mswiders, rrajasek

Target Milestone:

ER1

Keywords:

Regression

Target Release:

6.0.2

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2014-08-06 19:49:49 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:

Description	Flags
Maven project with reproducer	none

Description Marek Winkler 2014-03-04 15:54:14 UTC

Description of problem:

When calling signalEvent command, the process does not receive it. Please see the attached maven project with reproducer for details.

Version-Release number of selected component (if applicable):

BPMS 6.0.1.ER2

This is a regression, as it worked with 6.0.1 ER1.

How reproducible:

Please run mvn clean test on the attached maven project.


Actual results:

The test case fails.


Expected results:

The test passes.

Comment 1 Marek Winkler 2014-03-04 15:55:00 UTC

Created attachment 870485 [details]
Maven project with reproducer

Comment 2 Edson Tirelli 2014-03-04 16:15:46 UTC

Sorry, linked the tickets by mistake.

Comment 3 Maciej Swiderski 2014-03-04 16:27:34 UTC

Marek,

looking at the process it is actually not valid according to BPMN2 specification. We had recently made a fix to make it more accurate in terms of compliance with BPMN2 and that's why it now is failing on this process. 

extract from BPMN2 about intermediate events:
"
If the Intermediate Event is used within normal flow:
 -Intermediate Events MUST be a target of a Sequence Flow.

Note – this is a change from BPMN 1.2 semantics, which allowed some Intermediate Events to not have an incoming Sequence Flow.
"

So although the engine works properly it lacks meaningful validation to warn the user about incorrect usage scenario. So this requires enhancement in validation so it won't be possible to be built with such constructs.

Comment 4 Maciej Swiderski 2014-03-12 10:19:53 UTC

validation added so user will be warned early (on build time) that such construct is not allowed.

jbpm
master:
https://github.com/droolsjbpm/jbpm/commit/36d427fef0917b6d9e30ae83213f6533016afb9c

6.0.x:
https://github.com/droolsjbpm/jbpm/commit/e96b7ad547ac574261b8dc53fa7b447a5be17f3f

Comment 5 Ivo Bek 2014-05-05 08:16:37 UTC

Verified in BPMS 6.0.2.ER2