2 Replies Latest reply on Nov 15, 2005 7:05 AM by Alexander Serbul

    Phantom timeout

    Philip Wu Newbie

      I'm having a strange problem where a ejbTimer() event is fired, even though no Timer was scheduled to go off at that time.

      This only seems to occur in the following scenario.
      I create a scheduled timer event to go off. At this point ejbTimeout() is called. WHILE processing is still going on inside the ejbTimeout() method, I cancel the timer and recreate a new one with the same name but at a different time.
      Then the ejbTimeout() call is complete.
      This is where the problem shows up. Immediately after ejbTimeout() is done,
      I get ANOTHER call to ejbTimeout(). This is my phantom ejbTimeout(). Where did it come from? Any guesses? It can't be the new one i created because i set that one for 24 hours ahead of time.