0 Replies Latest reply on Oct 16, 2012 4:46 PM by nauvil

    EJB 3.1 Timer Service Fail Over

    nauvil

      I am thinking about porting a Spring Quartz based application to EJB 3.1 to see if EJB has improved.  I am having problems understanding how fail-over works with the Schedule Timer Service.  In Quartz, there are database tables which clustered Quartz instances use. If one node in your cluster crashes, jobs will still get executed on other nodes.  I have been looking at how the Timer Service persists things and it appears to use the file system of the server the Timer was created on.  Is this true?  I do not see how this would be possible as it would render the Timer Service unusable.  So i must be missing something. Can anyone help me out with this?