From the code you supplied I cannot see why the timer is not created (I'm
assuming that you're not using abstract classes as handlers and that the class
name for the task timer action handler does match in your actual code, because
otherwise you'd have other problems running your example). At a
Unfortunately your stack trace doesn't show the real (original) exception,
maybe there is a 'caused by' trace underneath it? But from this one, more
particular the line
at org.jbpm.graph.def.GraphElement.executeAction(GraphElement.java:276)
we are able to see that the exception originates in the
If your app wasn't multi-threaded, you wouldn't be running into these SOSE's -
because then you would have total control over when you start a transaction and
when you end it. There would be no overlap possible (unless you would program
it that way accidentally, of course).
You can find a
Michael, it looks like you're doing some custom asynchronous continuation, and
the moment in which the new transaction is started (i.e. the jBPM context
created) isn't related at all of the old transaction, which in a sense
'spawned' it - am I reading that correctly?
We have been doing
