Bug 781140 (SOA-3639) - [JBPM-2818] Leaving node in super-state throws org.jbpm.JbpmException: cannot leave Node without leaving transition
Summary: [JBPM-2818] Leaving node in super-state throws org.jbpm.JbpmException: cannot...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: SOA-3639
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBPM - within SOA, JBPM - standalone
Version: 5.0.0 CR1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ER4
: 5.3.0 GA
Assignee: Marco Rietveld
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-29 17:17 UTC by Len DiMaggio
Modified: 2019-03-03 17:40 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-10-15 17:25:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 779609 0 high CLOSED [JBPM-2818] Leaving node in super-state throws org.jbpm.JbpmException: cannot leave Node without leaving transition 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBPM-2818 0 Major Resolved Leaving node in super-state throws org.jbpm.JbpmException: cannot leave Node without leaving transition 2012-07-15 23:05:20 UTC
Red Hat Issue Tracker SOA-1979 0 Major Closed [JBPM-2818] Leaving node in super-state throws org.jbpm.JbpmException: cannot leave Node without leaving transition 2012-07-15 23:05:20 UTC
Red Hat Issue Tracker SOA-3639 0 Major Closed [JBPM-2818] Leaving node in super-state throws org.jbpm.JbpmException: cannot leave Node without leaving transition 2012-07-15 23:05:20 UTC

Internal Links: 779609

Description Len DiMaggio 2011-11-29 17:17:09 UTC
Affects: Documentation (Ref Guide, User Guide, etc.), Release Notes
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/491073
project_key: SOA

Platform JIRA for [JBPM-2818] Leaving node in super-state throws org.jbpm.JbpmException: cannot leave Node without leaving transition

Comment 1 Len DiMaggio 2011-11-29 17:17:09 UTC
Link: Added: This issue Cloned from SOA-1979


Comment 2 Suz 2012-06-15 04:18:57 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
When using JBPM, leaving a node in super-state mode throws an exception. This results in users being unable to leave the node without also leaving the transition.

Comment 3 Douglas Palmer 2012-06-29 10:14:01 UTC
This seems to have been fixed for ages; can we verify and close with 5.3.0.ER4?

Comment 4 David Le Sage 2012-07-02 03:51:43 UTC
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-When using JBPM, leaving a node in super-state mode throws an exception. This results in users being unable to leave the node without also leaving the transition.+If you left a jBPM node in super-state mode, an exception was thrown. This resulted in users being unable to leave the node without also leaving the transition.

Comment 5 Marek Baluch 2012-07-15 06:13:01 UTC
Verified on 5.3 ER5. See bellow log for more info. The log was made by a process which has the same structure as the one in JBPM-2818

08:10:57,042 DEBUG [Token] 'ESB_ASYNC_SIGNAL_ACTION' unlocked Token(1)
08:10:57,054 DEBUG [GraphElement] Token(1) fires event 'before-signal' on StartState(start)
08:10:57,057 DEBUG [GraphElement] Token(1) fires event 'node-leave' on StartState(start)
08:10:57,060 DEBUG [GraphElement] Token(1) fires event 'transition' on Transition(StartState(start)->Node(node1)
08:10:57,065 DEBUG [GraphElement] Token(1) fires event 'superstate-enter' on SuperState(super-state1)
08:10:57,066 DEBUG [GraphElement] Token(1) fires event 'node-enter' on Node(node1)
08:10:57,076 DEBUG [Script] script input: {node=Node(node1), theBody=*** RUN ***, token=Token(1), task=null, executionContext=ExecutionContext(null), taskInstance=null}
08:10:57,089 INFO  [STDOUT] @@@@@@@@@@@ Node1
08:10:57,091 DEBUG [GraphElement] Token(1) fires event 'before-signal' on Node(node1)
08:10:57,091 DEBUG [GraphElement] Token(1) fires event 'node-leave' on Node(node1)
08:10:57,094 DEBUG [GraphElement] Token(1) fires event 'transition' on Transition(Node(node1)->Node(node2)
08:10:57,095 DEBUG [GraphElement] Token(1) fires event 'node-enter' on Node(node2)
08:10:57,097 DEBUG [Script] script input: {node=Node(node2), theBody=*** RUN ***, token=Token(1), task=null, executionContext=ExecutionContext(null), taskInstance=null}
08:10:57,101 INFO  [STDOUT] @@@@@@@@@@@ Node2
08:10:57,103 DEBUG [GraphElement] Token(1) fires event 'before-signal' on Node(node2)
08:10:57,103 DEBUG [GraphElement] Token(1) fires event 'node-leave' on Node(node2)
08:10:57,104 DEBUG [GraphElement] Token(1) fires event 'superstate-leave' on SuperState(super-state1)
08:10:57,104 DEBUG [GraphElement] Token(1) fires event 'transition' on Transition(SuperState(super-state1)->EndState(end)
08:10:57,105 DEBUG [GraphElement] Token(1) fires event 'node-enter' on EndState(end)
08:10:57,107 DEBUG [GraphElement] Token(1) fires event 'process-end' on ProcessDefinition(jbpm2818)
08:10:57,131 DEBUG [GraphElement] Token(1) fires event 'after-signal' on Node(node2)
08:10:57,131 DEBUG [GraphElement] Token(1) fires event 'after-signal' on Node(node1)
08:10:57,131 DEBUG [GraphElement] Token(1) fires event 'after-signal' on StartState(start)


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