We've experiencing some problems regarding timers that don't get executed using
jBPM version 3.2.2 after a server crash.
It seems like that not alle timers are re-initiated after rebooting the
application server (ver. 4.2.2). This is getting a quite critical issue since
we have a lot of
I have a problem with the timers in the task.
I have defined:
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4200946#4200946
Reply to the post :
Hi,
there is not much documentation regarding the actual use of timers. I want to
implement a wait state which is left after the duration period. As I understood
from description the following should do it:
cancel-timer name='reminder'/
Hello.
I'm trying to ceate a simple console application with jbpm and timers. What I
did is quite simple:
public static void main(String[] args)
| {
| try
| {
| JbpmConfiguration conf =
JbpmConfiguration.getInstance(src/main/config/jbpm.cfg.xml);
|
Hi,
In a processdef, one fork leads to several states, each state has a timer
attached. The idea is to do concurrent async executions through the
TimerServiceBean. However, get exceptions, when those states changing to join
node.
anonymous wrote : Caused by:
Using jbpm 3.1.1, I am trying to accomplish the following:
1) Create a timer.
2) Execute some action as the result of the timer waking up and being serviced.
My question regards how to structure the business process in conjunction with
the proper setting of the timer's transition. I have
Bug:
When defining a node timer in the Eclipse plugin according to the rules of
Chapter 12, it says cvc-complex-type.2.4.b: The content of element 'timer' is
not complete. One of action , script is expected.
And it wont allow a deployment of the process.
It does not say this is a requirement
