This is how I end tasks:
If its a timer that signals the token and the task needs to therefore be
automatically ended then I also make sure the end-tasks= true attribute on the
task node is
1) The log file could be a problem... thanks
2) the token does reach the join and continues on through (we though the same
thing but upon testing and looking at what the database did, it worked)
3) there are two functional requirements:
a) I'll skip the batch processing functional requirements
1) there is a real persisted wait state (and its set from one minute to 19
days depending on the action taken by the user) but we have been getting stack
overflow errors (after running 24/7 for about 2 weeks) and then timers stop
working (we have to restart the application server) and this is c
Hi I new to the forum but have been using jBPM for a bit now (and loving it). I
have a couple "design pattern" questions to ask.
1) Should jBPM be used as a "fancy" server side batch processor/scheduler where
the token recurses from one processing node to a decision node and then, based
on the
