"dimitris(a)jboss.org" wrote : JBAS-4598 is an old report against 4.0.5 and many things changed in timers in 4.2.2+ | | Thinking more about this, maybe the moment you ask for the timers, those are not created yet? i.e. the target container where the timers belong has not fully started for it's timers to be there. Can you verify this is not the case, i.e. check for the timers after the deployment is complete, or see if you can configure a dependency. My EJB doesn't access the timers during the start up phase but always after the deplyoment is complete. So therefore there is no need to configure a dependency. A look into the defaultDB.log (in jboss.home\server\default\data) reveales the following disadvantageous behaviour on start up, 3 timers are deleted from table timers and recreated, but get different ids: DELETE FROM TIMERS WHERE TIMERID='1255087193422' AND TARGETID='[target=...,name=EETimerService,service=EJB3]' | DELETE FROM TIMERS WHERE TIMERID='1255087193423' AND TARGETID='[target=...,name=EETimerService,service=EJB3]' | DELETE FROM TIMERS WHERE TIMERID='1255087193424' AND TARGETID='[target=...,name=EETimerService,service=EJB3]' | INSERT INTO TIMERS VALUES('1255092103922','[target=...,name=EETimerService,service=EJB3]','2009-10-12 01:18:23.437000000',0,NULL,'aced00057372002464652e6d6574616672616d652e6a6162632e65652e74696d65722e54696d6572496e666f50fe499a85be42e10200045a00096578656354696d65724c00066272616e63687400124c6a6176612f6c616e672f537472696e673b4c000970726f6365737349647400104c6a6176612f6c616e672f4c6f6e673b4c000573696249647400134c6a6176612f6c616e672f496e74656765723b78700074000774696d656f75747372000e6a6176612e6c616e672e4c6f6e673b8be490cc8f23df0200014a000576616c7565787200106a6176612e6c616e672e4e756d62657286ac951d0b94e08b02000078700000000000450002737200116a6176612e6c616e672e496e746567657212e2a0a4f781873802000149000576616c75657871007e000700000000') | INSERT INTO TIMERS VALUES('1255092103923','[target=...]','2009-10-12 01:18:27.296000000',0,NULL,'aced00057372002464652e6d6574616672616d652e6a6162632e65652e74696d65722e54696d6572496e666f50fe499a85be42e10200045a00096578656354696d65724c00066272616e63687400124c6a6176612f6c616e672f537472696e673b4c000970726f6365737349647400104c6a6176612f6c616e672f4c6f6e673b4c000573696249647400134c6a6176612f6c616e672f496e74656765723b78700074000774696d656f75747372000e6a6176612e6c616e672e4c6f6e673b8be490cc8f23df0200014a000576616c7565787200106a6176612e6c616e672e4e756d62657286ac951d0b94e08b02000078700000000000450004737200116a6176612e6c616e672e496e746567657212e2a0a4f781873802000149000576616c75657871007e000700000000') | INSERT INTO TIMERS VALUES('1255092103924','[target=...]','2009-10-12 01:18:32.656000000',0,NULL,'aced00057372002464652e6d6574616672616d652e6a6162632e65652e74696d65722e54696d6572496e666f50fe499a85be42e10200045a00096578656354696d65724c00066272616e63687400124c6a6176612f6c616e672f537472696e673b4c000970726f6365737349647400104c6a6176612f6c616e672f4c6f6e673b4c000573696249647400134c6a6176612f6c616e672f496e74656765723b78700074000774696d656f75747372000e6a6176612e6c616e672e4c6f6e673b8be490cc8f23df0200014a000576616c7565787200106a6176612e6c616e672e4e756d62657286ac951d0b94e08b02000078700000000000450006737200116a6176612e6c616e672e496e746567657212e2a0a4f781873802000149000576616c75657871007e000700000000') | This explaines why new timers can be accessed by handles when jboss keeps running, and can not after a restart. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4259626#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...