The issue is that the quartz-based timer service has some issues with some database
backends and it's not very well tested in the community. There also discussion on how
to proceed with an improved timer service for ejb3.1. Until those are finalized I'd
suggest to stick with the ejb2 timer service.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4212022#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...