[ https://jira.jboss.org/browse/JBAS-8232?page=com.atlassian.jira.plugin.sy... ] jaikiran pai commented on JBAS-8232: ------------------------------------ Thanks, I'll take a look. Jamie, by the way, does your logs show that the timer.cancel() is indeed being called? Also if you have your application logs and/or the server logs, please attach them here. I'll in the meantime try to reproduce this in a testcase -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8232?page=com.atlassian.jira.plugin.sy... ] jaikiran pai commented on JBAS-8232: ------------------------------------ Jamie, That indeed was a bug which I was able to reproduce in a testcase and fix it. I even have released a newer version of timerservice. The bug was a result of a combination of getTimers() and cancel() implementation. It should be fixed now. The testcase has been added (similar to what you have here) http://github.com/jbossejb3/jboss-ejb3-timerservice/tree/master/testsuite.... I have released the fix. Could you try the following steps and see if it works for you: The following steps are against the JBoss AS latest snapshot (or the one you already have): (Stop the server, if it's already running) 1) Take a backup of jboss-ejb3-timerservice-mk2.jar from JBOSS_HOME/server/< servername>/deploy folder 2) Remove timer jboss-ejb3-timerservice-mk2.jar from JBOSS_HOME/server/< servername>/deploy folder 3) Download the timerservice jar from here https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... 4) Copy it to JBOSS_HOME/server/< servername>/deploy and rename it to jboss-ejb3-timerservice-mk2.jar 5) Start the server and run your app/tests. This however, isn't yet in JBoss AS trunk and I am not sure whether it will make it to M4 (the code freeze for M4 was yesterday). I'll see if the window is still open for this fix. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8232?page=com.atlassian.jira.plugin.sy... ] jaikiran pai commented on JBAS-8232: ------------------------------------ Jamie, Thanks for testing the fix. The fix has been applied to AS trunk and has also been added to the M4 branch from where 6.0.0.M4 will be released. So this fix is going to make it to M4. Thank you for this timely bug report. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBAS-8232?page=com.atlassian.jira.plugin.sy... ] jaikiran pai updated JBAS-8232: ------------------------------- Affects Version/s: (was: 6.0.0.M4) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira