TaskTimerExecutionDbTest - proper jbpmConfiguration is not passed to SchedulerThread ------------------------------------------------------------------------------------ Key: JBPM-680 URL: http://jira.jboss.com/jira/browse/JBPM-680 Project: JBoss jBPM Issue Type: Bug Affects Versions: jBPM 3.1.1 Environment: WebSphere v5.1 Test Environment under WSAD 5.1.2 DB2 v7 and MySql Windows XP Java 1.4.2_06 Reporter: Chris OBrien Assigned To: Tom Baeyens Priority: Critical In the test - TaskTimerExecutionDbTest .testTimerExecution throws: junit.framework.AssertionFailedError: expected:<1> but was:<0> In the test - TaskTimerExecutionDbTest.testTimerExecutionRepeat throws: org.jbpm.JbpmException: closed JbpmContext more then once... check your try-finally's around JbpmContexts blocks I am using a custom jbpmConfiguration (changed my jbpm.test.cfg.xml to reference a db2.hibernate.cfg.xml instead of the default), but it does not get passed to the SchedulerThread. Creating a new SchedulerThread with the default constructor ends up using the default configuration/context. This causes the test to fail, as it is querying the wrong database inside the SchedulerThread when it looks for all due timers. Changing lines 146 and 185 from: new SchedulerThread().executeTimers(); to: new SchedulerThread( jbpmConfiguration ).executeTimers(); ...fixes both the tests from failing.