Your stack trace looks indeed close to the one I had.
Look maybe how often the commits are made. Try to commit more frequently to
see if you still get this error. I don't know what else to say.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3945587#3945587
Re
"julian_k" wrote : The strange thing is that this code will cause a deadlock
sometimes, and not others.
Do you know when a deadlock occurs and when it does not ? Is there every time
only one transition fired during your session ? Or is there several sometimes
several ones for the same process i
As I said, when entering a task more than once (k is the number of time the
node was reached), a cancellation of the task was made in order not to ask for
some information already gathered.
anonymous wrote : if (k>1) {
| ti.cancel();
| return;
| }But such a can
well,
the transition to a previously left node was in fact taken, but the task which
was binded to this node was declared ended (by a taskInstance.cancel() ) as
soon as we entered into the node. The default transition was immediatly fired.
The SQL error came when comitting the transaction : the
I found the reason of this behaviour. It is not a bug in jbpm, neither in the
mysql-connector but a bad programming from the earlier developper of the
application I am working on.
So problem solved.
Thank you for your interest.
Regards,
Eric
View the original post :
http://www.jboss.com/inde
I also experiment deadlocks, but they occur each time (and only these times) I
want to take a transition leading to a node that has already been visited. It
happens on the commit when I want to close the JBPMSession. I'm using Jbpm
3.0.2, mysql-connector-java 3.0.11 and mysql 4.1.18 .
Here is
I have a more practical question: how to include a sub process ? Does it have
to be defined in the same processdefinition.xml file as the main process ? With
the same tag or is there a special tag for a sub process ?
Thanks in advance for your answers.
View the original post :
http://www.jboss
I am wondering whether it is possible possible to have cycles in workflow with
JBoss Jbpm, i.e. can a state be re-entered during a process ?
I tried to define such a workflow in my processdefinition.xml file. No error
occurs, but the transition leading to a previous state are not executed.
Does
