Can you tell us more about the GlassFish version that you are using, how the
timer is created, and the exact steps you are performing?
Are you disabling/enabling a single bean (I don't think it's possible) or the
whole app?
When the app or bean is re-enabled, how well before 12:30:00 it's done? There is
a (configurable) delay time between the timer is created (or between 2
consecutive expiration of the same timer) so that the timers do not expire more
often than the container can handle - see 'minimum-delivery-interval-in-millis'
in domain.xml which is set to 7000 millis in v2.x. Can it explain the 8 seconds
delay?
thanks,
-marina
glassfish_at_javadesktop.org wrote:
> Since I've created and developed my timer bean. I've found a problem with it. Right now our clients wants a enable/disable ability in the admin console. So they want to start and stop the bean when they can.
>
> During the test stages. I'm getting this. Let's say if I wanted the bean to go at 12:30 on the same day.
>
> First time -> 12:30:00 -> correct... which this is what I want
>
> Running the client again.
> Second time -> bean is cancel(timer is canceled but not the timerService.
>
> Running the client for a third time(about a 8 second relapse).
> Third time -> 12:30:08 -> adding seconds
>
> I'm using TimerService which I don't think there is a way to do this. However, I'm wondering if there is a way to keep this from happening. I'm running out of ideas on my end here. Can anyone explain or help me with this?
>
> I'll post the code upon request...
> [Message sent by forum member 'tannic2k7' (daniel.crain_at_us.army.mil)]
>
> http://forums.java.net/jive/thread.jspa?messageID=363381
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>