Bug 826515 - WorkItem cannot be added to adhoc process - Unknown node id: 0
WorkItem cannot be added to adhoc process - Unknown node id: 0
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: jBPM 5 (Show other bugs)
BRMS 5.3.0.GA
Unspecified Unspecified
unspecified Severity medium
: ---
: future
Assigned To: Kris Verlaenen
Radovan Synek
Depends On:
  Show dependency treegraph
Reported: 2012-05-30 07:49 EDT by Radovan Synek
Modified: 2012-05-30 08:23 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Radovan Synek 2012-05-30 07:49:46 EDT
Description of problem:
After adding new work item to adhoc process instance, exception occurs when trying to fire event: eventSupport.fireBeforeNodeTriggered(workItemNodeInstance, session);

Similar exception is thrown from:
session.getWorkItemManager().completeWorkItem(wi.getId(), new java.util.HashMap<String, Object>());

This issue is thanks to Kris already fixed in project - master branch (there is also the test case):

Unknown node id: 0
at org.jbpm.workflow.core.impl.WorkflowProcessImpl.getNode(WorkflowProcessImpl.java:50)
at org.jbpm.workflow.core.impl.WorkflowProcessImpl.internalGetNode(WorkflowProcessImpl.java:54)
at org.jbpm.workflow.instance.impl.NodeInstanceImpl.getNode(NodeInstanceImpl.java:100)
at org.jbpm.workflow.instance.node.WorkItemNodeInstance.getNodeName(WorkItemNodeInstance.java:306)
at org.jboss.qa.brms.jbpm.tools.DebugProcessEventListener.formatNodeMessage(DebugProcessEventListener.java:75)
at org.jboss.qa.brms.jbpm.tools.DebugProcessEventListener.beforeNodeTriggered(DebugProcessEventListener.java:55)
at org.drools.event.ProcessEventSupport.fireBeforeNodeTriggered(ProcessEventSupport.java:88)

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