I've had similar errors using EJB Timers. I believe what is going on is that your application server is managing your transactions but that is not getting communicated to jBPM's Hibernate.
Since my timer's logic was simple and purely jBPM related, I solved the problem by letting the bean manage its own transactions. With EJB3 you can tag the bean with: | @TransactionManagement(TransactionManagementType.BEAN) | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3922390#3922390 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3922390 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
