5 Replies Latest reply on Dec 13, 2004 3:25 AM by Stefano Sambi

    Another problem with Timer Service: duplication

    Stefano Sambi Newbie

      I've another problem with Timer Service, and I hope the last one.

      I've launched automatically my Timer Service when my application starts, that is in a Servlet Context Listener, as described in http://radio.weblogs.com/0135826/2004/09/21.html.

      I've noticed that my timer service is duplicated, so my bean's EjbTimeout method is invoked twice.
      I think this is due because of database persistence: my application launches the timer service, the server stores it in db and then the server recovers and launches timer services stored in db.

      I don't know if this is a bug or I did some inaccuracies; the latter is more probable, so I thank anyone can help me.