[jbpm-issues] [JBoss JIRA] Commented: (JBPM-1166) fix SEAM timer transaction integration

[ http://jira.jboss.com/jira/browse/JBPM-1166?page=comments#action_12411608 ] Tom Baeyens commented on JBPM-1166: ----------------------------------- First I added transaction demarcation manually around the executeTimer in the job executor. Second I added <transaction:ejb-transaction /> in the seam components as a suggestion from Pete. This got rid of most of the problems. Now the full test process executes and ends. But still we're seeing this after the synchronization executed. The good part is that it's no longer a tx problem :-) Pete, (or any of the other SEAM guys) can you give me insight in how the jBPM timer thread can *set* the ManagedJbpmContext ? Cause the timer thread creates it's own transaction and it's own JbpmContext. Then I want SEAM to expose the same JbpmContext that was created by the timer thread. So the question is: Is there a way for jBPM to programmatically set the ManagedJbpmContext ? Does that make sense to do it that way ? 16:22:24,531 DEBUG [DbPersistenceService] closing hibernate session 16:22:24,531 DEBUG [Services] closing service 'tx': org.jbpm.tx.TxService@4ee543 16:22:24,531 DEBUG [Services] closing service 'scheduler': org.jbpm.scheduler.db.DbSchedulerService@1adc735 16:22:24,531 DEBUG [Services] closing service 'logging': org.jbpm.logging.db.DbLoggingService@1f172aa 16:22:24,531 DEBUG [JtaTransactionHandler] beginning a JTA transaction 16:22:24,531 DEBUG [JndiUtil] fetched 'org.jboss.tm.usertx.client.ServerVMClientUserTransaction@1e4be04' from JNDI location 'java:comp/UserTransaction' 16:22:24,531 DEBUG [JtaTransactionHandler] committing the JTA transaction 16:22:24,531 DEBUG [JobSession] deleting timers for process instance org.jbpm.graph.exe.ProcessInstance@815988 16:22:24,531 INFO [STDOUT] Hibernate: delete from JBPM_JOB where CLASS_='T' and PROCESSINSTANCE_=? 16:22:24,546 DEBUG [JobSession] 0 remaining timers for 'org.jbpm.graph.exe.ProcessInstance@815988' are deleted 16:22:24,546 DEBUG [JobSession] deleting execute-node-jobs for process instance org.jbpm.graph.exe.ProcessInstance@815988 16:22:24,546 INFO [STDOUT] Hibernate: delete from JBPM_JOB where CLASS_='N' and PROCESSINSTANCE_=? 16:22:24,562 DEBUG [JobSession] 0 remaining execute-node-jobs for 'org.jbpm.graph.exe.ProcessInstance@815988' are deleted 16:22:24,562 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] TwoPhaseCoordinator.afterCompletion - returned failure for com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@1ba8574 16:22:24,562 WARN [arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator_4] TwoPhaseCoordinator.afterCompletion - returned failure for com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple@8fbf0e 16:22:24,578 ERROR [JobExecutorThread] exception in job executor thread. waiting 5000 milliseconds org.jbpm.JbpmException: closed JbpmContext in different order then they were created... check your try-finally's around JbpmContexts blocks at org.jbpm.JbpmConfiguration.popJbpmContext(JbpmConfiguration.java:580) at org.jbpm.JbpmConfiguration.jbpmContextClosed(JbpmConfiguration.java:592) at org.jbpm.JbpmContext.close(JbpmContext.java:144) at org.jbpm.job.executor.JobExecutorThread.executeJob(JobExecutorThread.java:205) at org.jbpm.job.executor.JobExecutorThread.run(JobExecutorThread.java:68) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira