[jBPM] - Old JBPM (ver 3.2.7) non-logical exception "org.jbpm.JbpmException: transition 'no-work-done' does not exist on Node(preScan)"
by David Edery
David Edery [https://community.jboss.org/people/d_edery] created the discussion
"Old JBPM (ver 3.2.7) non-logical exception "org.jbpm.JbpmException: transition 'no-work-done' does not exist on Node(preScan)""
To view the discussion, visit: https://community.jboss.org/message/717230#717230
--------------------------------------------------------------
Hi
We are using JBPM 3.2.7 in our large-scale application for a long time now.
Recently, due to race-conditions with the DB commit we have decided to move from persistent mode (in which all the process-definitions, process-instances etc... were stored in the DB) to non-persistent that works in the following flow:
1. We read all the .xml files containing process definitions.
2. For each .xml file we create a process definition and store it in a static map.
3. When the user wants to activate a flow (it's usually the same flow on multiple targets) - *we create a new ProcessInstance based on the same instance of ProcessDefinition* (this might explain the phenomena but we didn't see how from the code).
4. Each thread in a dedicated thread pool takes one ProcessInstance and activates it (via .signal).
5. Each action calls the .signal (with or without transition name) in the end of its business logic - thus creating a synchronized workflow.
Recently we have encountered a problem (it occurred only one time) that caused failure in some of the targets (ProcessInstances).
The exception was (full stack-trace attached to the discussion, highlighted lines describe the flow):
*org.jbpm.JbpmException: transition 'no-work-done' does not exist on Node(preScan)*
at org.jbpm.graph.exe.*Token.signal*(Token.java:170)
at com.yyyy.nms.massconfig.swdownload.*PreScanAction.run*(PreScanAction.java:42)
at com.yyyy.nms.massconfig.common.*BaseAction.execute*(BaseAction.java:71)
at org.jbpm.graph.def.Action.execute(Action.java:137)
at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:280)
at org.jbpm.graph.def.Node.execute(Node.java:395)
at org.jbpm.graph.def.Node.enter(Node.java:375)
at org.jbpm.graph.def.Transition.take(Transition.java:151)
at org.jbpm.graph.def.Node.leave(Node.java:453)
at org.jbpm.graph.exe.Token.signal(Token.java:214)
at org.jbpm.graph.exe.*Token.signal*(Token.java:143)
at com.yyyy.nms.massconfig.common.*FirstWorkflowAction.run*(FirstWorkflowAction.java:94)
at com.yyyy.nms.massconfig.common.*BaseAction.execute*(BaseAction.java:71)
at org.jbpm.graph.def.Action.execute(Action.java:137)
at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:280)
at org.jbpm.graph.def.Node.execute(Node.java:395)
at org.jbpm.graph.def.Node.enter(Node.java:375)
at org.jbpm.graph.def.Transition.take(Transition.java:151)
at org.jbpm.graph.def.Node.leave(Node.java:453)
at org.jbpm.graph.node.StartState.leave(StartState.java:78)
at org.jbpm.graph.exe.Token.signal(Token.java:214)
at org.jbpm.graph.exe.*Token.signal*(Token.java:143)
at org.jbpm.graph.exe*.ProcessInstance.signal*(ProcessInstance.java:287)
at com.yyyy.nms.jbpmworkflow.*JbpmWorkflowInvoker*.startNonPersistentWorkflow(JbpmWorkflowInvoker.java:271)
at com.yyyy.nms.jbpmworkflow.*JbpmWorkflowInvoker*.startWorkflow(JbpmWorkflowInvoker.java:350)
at com.yyyy.nms.jbpmworkflow.StartWorkflowMDB.signalWorkflow(StartWorkflowMDB.java:101)
at com.yyyy.nms.jbpmworkflow.*StartWorkflowMDB*.handleMessage(StartWorkflowMDB.java:85)
In the .xml file from which the related ProcessDefinition was read looks like this (in the relevant part):
<exception-handler>
<action class="com.yyyy.nms.massconfig.common.ExceptionAction" />
</exception-handler>
<start-state>
<transition to="check-suspend-or-abort"></transition>
</start-state>
<node name="check-suspend-or-abort">
<action class="com.yyyy.nms.massconfig.common.FirstWorkflowAction" />
<transition to="preScan"/>
<transition to="error" name="error"/>
<transition to="suspended" name="suspended"/>
<transition to="aborted" name="aborted"/>
</node>
<node name="preScan" description="Pre-upgrade Scan" shouldField="preScan">
<action class="com.yyyy.nms.massconfig.swdownload.PreScanAction" />
<event type="node-enter">
<action class="com.yyyy.nms.massconfig.common.StepStartAction" />
</event>
<transition to="acquireFtpForUpload">
<action class="com.yyyy.nms.massconfig.common.StepDoneAction" />
</transition>
<transition to="acquireFtpForUpload" name="no-work-done">
<action class="com.yyyy.nms.massconfig.common.StepSkippedAction" />
</transition>
<transition to="error" name="error"/>
<transition to="suspended" name="suspended"/>
<transition to="aborted" name="aborted"/>
</node>
As you can see, if we are in the "preScan" node - we definitely have the "no-work-done" transition.
The scenario that produced this exception contained 40 process instances (=40 different targets) based on the same ProcessDefinition instance. Out of which 7 targets failed on this exception and the rest (which went through the same nodes and transitions) completed successfully (before and after the 7 failed).
The only clue to a possible problem was that the JBPM exception thrown for all 7 targets was thrown *at the same exact time* (same millisecond even). Meaning - all 7 tried to perform the .signal("no-work-done") in the PreScanAction at the same exact time.
We have generated the same scenario on our development environment (using CountDownLatch in the prior to the .signal("no-work-done")) with 10 targets that wait together and all of them call the .signal("no-work-done") in the same exact millisecond - the failure was not reproduced.
Our question is - did you encounter such scenario? If so - was it fixed in newer versions? can we bypass it? (I thought about creating a new ProcessDefinition per ProcessInstance - this will cost a lot in terms of memory consumption and CPU load - but since I couldn't reproduce the problem, I'm not sure that it will solve it).
Oh, we create the ProcessDefinitions map during server load. We don't change them after the creation of the map.
As you can see in the attached screenshot (from LogMX) - this is how it looks like, 7 different threads throw the same exception on the same time.
https://community.jboss.org/servlet/JiveServlet/showImage/2-717230-17993/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-717230-17...
Thank you for your time.
Sincerely
David Edery.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/717230#717230]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years, 1 month
[jBPM] - Re: Adding new workitems programmatically, without repacking the application ?
by Arun V G
Arun V G [https://community.jboss.org/people/arunvg] created the discussion
"Re: Adding new workitems programmatically, without repacking the application ?"
To view the discussion, visit: https://community.jboss.org/message/717137#717137
--------------------------------------------------------------
Thanks for the very quick reply.
Hope you are pointing to the registerWorkItemHandler(String workItemName, WorkItemHandler handler); I am using this to register the handler.
*Does it means that the workdefinitions like below has no meaning in the core engine part and is used only by the editor.*
import org.drools.process.core.datatype.impl.type.StringDataType;
[
// the Notification work item
[
"name" : "Notification",
"parameters" : [
"Message" : new StringDataType(),
"From" : new StringDataType(),
"To" : new StringDataType(),
"Priority" : new StringDataType(),
],
"displayName" : "Notification",
"icon" : "icons/notification.gif"
]
]
Cheers :)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/717137#717137]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years, 1 month
[jBPM] - Adding new workitems without repacking the application ?
by Arun V G
Arun V G [https://community.jboss.org/people/arunvg] created the discussion
"Adding new workitems without repacking the application ?"
To view the discussion, visit: https://community.jboss.org/message/717125#717125
--------------------------------------------------------------
I am working with creating domain specific processes and followed the example
* Created work definition in the MVEL format
* Register the workdefinition in the drools.rulebase.conf
* Creating the work item handler
* Registering the workitem hanlder.
And it worked effectively.
Our requirment is to create new work definitions using an editor and save the attribtes of a work definition in a Database so that in future it can be edited or extended
So my questions are
* Can I create a Work definition in any other format other than the MVEL .( I don't want to be a polyglot :) )
* Can I register the Work item to the processing engine programatically rather than having the drools.rulebase.conf file in the class path.
I am not very concerned about the eclipse/web editor as we have plans to develop it in house and we are evaluating jBPM for the processing part.
Any hints would be highly appreciated
Cheers :)
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/717125#717125]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years, 1 month
[JBoss Messaging] - JBoss Messaging replicated queue issue
by sachin.garg
sachin.garg [https://community.jboss.org/people/sachin.garg] created the discussion
"JBoss Messaging replicated queue issue"
To view the discussion, visit: https://community.jboss.org/message/717068#717068
--------------------------------------------------------------
Hi,
I am using JBOSS messaging in the following way:
1) Two JBOSS instances using 'all' config
2) One replicated queue created on each JBOSS instance (clustered = true)
3) one producer attach locally to the queue on each instance (i.e. both the producer on both the nodes keep on adding messages to this replicated queue)
4) One JBOSS instance is marked as "consumer node" and queue message consumer is started on only this node (i.e. messages will be consumed on only one node). There is a logic which will decide which JBOSS instance is marked as "consumer node"
5) PostOffice used is clustered
6) server peer configured to not enforce message sequencing.
7) produced messages are non-persistent (deliveryMode = NON_PERSISTENT)
But I am facing problem with this. Messages produced on "non consumer node" do not get replicated to the queue on the "consumer node" and hence not available for consumption.
I enabled the logging and checked that postoffice finds two queues but only delivers to the local queue as it discovers that the remote queue is recoverable.
Any idea how to set it working?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/717068#717068]
Start a new discussion in JBoss Messaging at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
14 years, 1 month
