[CAM-8072] Exposing local variable via output mapping fails on parallel gateway with async after Created: 26/Jul/17  Updated: 30/Aug/17  Resolved: 01/Aug/17

Status: Closed
Project: camunda BPM
Component/s: engine
Affects Version/s: 7.7.1, 7.8.0-alpha2
Fix Version/s: 7.8.0, 7.8.0-alpha3, 7.7.3

Type: Bug Report Priority: L3 - Default
Reporter: Johannes Heinemann Assignee: Svetlana Dorokhova
Resolution: Fixed Votes: 0
Labels: SUPPORT
Remaining Estimate: 0 minutes
Time Spent: Not Specified
Original Estimate: 0 minutes

Attachments: PNG File Diagram.png     Text File ErrorLog.txt    
Issue Links:
Depedendency

 Description   
  • given:
    • I expose a local variable via output mapping
  • when:
    • I use this variable after a parallel gateway with async after (see attached screenshot Diagram.png)
  • then:
    • I get the attached error message (see attached log ErrorLog.txt)
  • expected:
    • I can access the variable without any problems

Hint:



 Comments   
Comment by Smirnov Roman [ 27/Jul/17 ]

I think the problem is, that the flag isConcurrentLocal on the exposed variable is set to true. When the parallel gateway will be executed a concurrent execution will be created and the exposed variable is moved to the concurrent execution (see [1]).

[1]: https://github.com/camunda/camunda-bpm-platform/blob/master/engine/src/main/java/org/camunda/bpm/engine/impl/persistence/entity/ExecutionEntity.java#L1119

Generated at Wed Sep 20 04:06:11 CEST 2017 using JIRA 6.4.6#64021-sha1:33e5b454af4594f54560ac233c30a6e00459507e.