I'm experiencing the same problem -
using jboss-4.0.0DR3, i've successfully created a session bean that creates a timer - the ejbTimeout method is invoked as expected. but when the server is restarted the jboss trace reports:
17:23:03,281 INFO [FilePersistenceManager] Using data directory: D:\Java\jboss-4.0.0DR3\server\all\data
17:23:03,281 INFO [FilePersistenceManager] Open backup file: D:\Java\jboss-4.0.0DR3\server\all\data\timers.0.save
17:23:03,297 INFO [FilePersistenceManager] Load saved timers for container: jboss.j2ee:jndiName=CdrUploaderBean,service=EJB
17:23:03,313 INFO [FilePersistenceManager] Got saved timer item: FilePersistenceManager.TimerItem [ , type: ADD, timer rep: ContainerTimerRepresentative [ Id: 0, key: [B@c5e2cf, start date: Wed May 05 17:21:14 BST 2004, interval: 60000, info: [B@1adb7b8 ] ]
17:23:03,328 INFO [FilePersistenceManager] Started jboss:service=TimePersistenceManager,type=File
17:23:03,328 INFO [SchedulerTimerSource] Started jboss:service=EJBTimerService
yet the ejbTimeout is never called.
Is the fact the the timer is not being invoked after a restart of the server some missing functionality, or is it a bug on my part?
thanks in advance