[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-827) creating timers inside start() creates duplicate timers.

David Owens (JIRA) jira-events at jboss.com
Fri Jan 5 15:41:27 EST 2007


     [ http://jira.jboss.com/jira/browse/EJBTHREE-827?page=all ]

David Owens updated EJBTHREE-827:
---------------------------------

    Attachment: SimpleTimer.zip

1) Unzip
2) ant jar
3) copy the SimpleTimer.jar to the deploy directory.

> creating timers inside start() creates duplicate timers.
> --------------------------------------------------------
>
>                 Key: EJBTHREE-827
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-827
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>         Environment: Windows 2000, JBoss 4.0.5 (jems installer), Java 1.5
>            Reporter: David Owens
>         Attachments: SimpleTimer.zip
>
>
> Calling ctx.getTimerService().createTimer(...) within the start() method of a managed service bean creates duplicate timers.  In other words, I have a bean which is both @Management and @Service which has a method which is @Timeout.  In the start method of the bean (when the bean is deployed) I create a new timer.  But then the method marked @Timeout is called twice.  When I investigate the timers in by calling ctx.getTimerService().getTimers(), I find there are actually 2 timers with different ids, but with the exact same info.
> I have attached an example.  You will see the start() method getting called once when the bean is deployed, but then the timeout method getting called twice.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list