Hi All,
The current schedule processes all due timers in a single transaction. As result, it rollbacks all timers' work due to an exception in one of the timers. It's a problem:
- when you work with nontransactional resources as file system.
- if you have long lasting transaction, the total length of transaction processing can extend transaction timeout easily.
http://jira.jboss.org/jira/browse/JBPM-452
Strange that so many people think they are the first to encounter certain things. search the forum and jira first before reporting issues.