This will be addressed as part of StartEvent Timer Trigger in the API
https://jira.jboss.org/jira/browse/JBPM-1658
Thanks for the feedback
Ok,
I will check that out, pretty much getting sick of the timer troubles with jbpm - jboss
Finally replaced the EJB timer stuff with a scheduler to now be bitten by:
https://jira.jboss.org/jira/browse/JBPM-995
Offcourse I need transactions over these actions so the proposed workaround for this bug to alter the LOG level is useless if you use transactions.
So this leads me to the conclusion, and yeah this does work, that the jobexecutor can only currently run with ONE thread......
Regards,
Leo
??? I mis the relation between the log level and transactions.... But I'm kind of tired so that might be me...
Well,
If the workaround to get rid of the exceptions happening is to lower the log level ie you dont see them anymore that only gets rid of the log entry.
If you use transactional service from within your timers ie handlers with services that use transactions they will fail on the transactions because the exceptions that are thrown... at least in my situation.
So i dunno, had a shitty day so far on this again.... Pretty much renders timers useless in any enterprise transactional scenario.
Leo
"kukeltje" wrote:
??? I mis the relation between the log level and transactions.... But I'm kind of tired so that might be me...