[ 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

[ http://jira.jboss.com/jira/browse/JBPM-1166?page=comments#action_12411694 ] Tom Baeyens commented on JBPM-1166: ----------------------------------- that's what i was trying to do: include configurations so that we can make the jbpm job executor work in a seam environment. no ? i took as a basis the existing jBPM job executor. now, i'm trying to hack the necessary SEAM interceptions and SEAM stuff in there. inheritence could also be used. so that the basic jBPM job executor calls out to some overridable methods. then SEAM could buid a "SeamJobExecutor extends JobExecutor" as far as i can see, the approach you describe is approx the same. the question still remains as to what the specific SEAM behaviour should be. especially the JbpmContext that is created in the job executor thread in relation to the ManagedJbpmContext. afaik, that should be the last issue that needs customization in a SEAM env. regards, tom. -- 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

[ https://jira.jboss.org/jira/browse/JBPM-1166?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-1166: ----------------------------------- just talked to Pete about this. Ideally, the job executor should use a org.jboss.seam.async.Asynchronous$ContextualAsynchronousRequest to execute a timer in a seam environment. In the process method, first, the UserTransaction should be fetched and managed around executing the timer. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1166?page=com.atlassian.jira.plug... ] Tom Baeyens updated JBPM-1166: ------------------------------ Fix Version/s: jBPM 3.3.0 GA -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1166?page=com.atlassian.jira.plug... ] Tom Baeyens commented on JBPM-1166: ----------------------------------- jbpm modifications done. waiting for SEAM team to verify if this customizability of the job executor can be configured and used effectively. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1166?page=com.atlassian.jira.plug... ] Thomas Diesler commented on JBPM-1166: -------------------------------------- [tdiesler@tdvaio trunk]$ mvn -o -Ddatabase=mysql -Dtest=JobExecutorCustomizationTest test Running org.jbpm.seam.JobExecutorCustomizationTest Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 7.373 sec <<< FAILURE! Results : Tests in error: testCustomJobExecutor(org.jbpm.seam.JobExecutorCustomizationTest) Tests run: 1, Failures: 0, Errors: 1, Skipped: 0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1166?page=com.atlassian.jira.plug... ] Tom Baeyens resolved JBPM-1166. ------------------------------- Resolution: Done verified locally against mysql. also the matrix doesn't indicate a problem with this test -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1166?page=com.atlassian.jira.plug... ] Thomas Diesler updated JBPM-1166: --------------------------------- Fix Version/s: jBPM 3.3.1 GA Reopened to get fixed for 3.3.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBPM-1166?page=com.atlassian.jira.plug... ] Ronald van Kuijk updated JBPM-1166: ----------------------------------- Fix Version/s: jBPM 3.3.2 GA (was: jBPM 3.3.0 GA) 3.3.1 is already out and this is still targeted at 3.3.0.GA. Moving to 3.3.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBPM-1166?page=com.atlassian.jira.plugin.sy... ] Alejandro Guizar resolved JBPM-1166. ------------------------------------ Labels: executor jbpm3 job seam timer (was: ) Assignee: Alejandro Guizar Fix Version/s: (was: jBPM 3.2.x) Resolution: Out of Date JobExecutorCustomizationTest is no longer excluded. All databases pass this test. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira