I'll skip the definition. If it isn't on the road map, it can't be near future
;-).
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867869#3867869
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867869
---
Define near future. Nothing exists on the roadmap currently.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867801#3867801
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867801
Are there plans to add timer server clustering in the near future?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867724#3867724
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867724
--
No, the ejb timer service currently has no clustering.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3867710#3867710
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3867710
--
If you wrap the timer as a singleton (deploy.singleton) then ti will get picked
up on a different host when X crashes. This assume schedules are stored in a
shared storage area, e.g. the DB.
Oops, I'm talking JBoss Scheduler here, don't know much about EJB Timers,
probably the above applies too
