[jboss-jira] [JBoss JIRA] Updated: (JBAS-3127) org.jboss.varia.scheduler.ScheduleManager.ScheduleInstance.stop() called twice

Dimitris Andreadis (JIRA) jira-events at jboss.com
Wed Jul 26 05:20:11 EDT 2006


     [ http://jira.jboss.com/jira/browse/JBAS-3127?page=all ]

Dimitris Andreadis updated JBAS-3127:
-------------------------------------

    Fix Version/s: JBossAS-4.0.6.CR1
                       (was: JBossAS-4.0.5.CR1)

> org.jboss.varia.scheduler.ScheduleManager.ScheduleInstance.stop() called twice
> ------------------------------------------------------------------------------
>
>                 Key: JBAS-3127
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3127
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Other
>    Affects Versions: JBossAS-4.0.3 SP1
>            Reporter: Dimitris Andreadis
>             Fix For: JBossAS-4.0.6.CR1
>
>
> A bogus exception is thrown when shutting down the server in the all (clusterred) configuration:
> 21:03:16,609 INFO  [Server] Runtime shutdown hook called, forceHalt: true
> 21:03:16,609 INFO  [Server] JBoss SHUTDOWN: Undeploying all packages
> 21:03:16,619 ERROR [ScheduleManager] Could not stop a Schedule
> javax.management.ListenerNotFoundException: Listener not found org.jboss.varia.s
> cheduler.ScheduleManager$MBeanListener at 9d2f26 for object name jboss:service=Timer
>         at org.jboss.mx.notification.MBeanServerListenerRegistry.remove(MBeanServerListenerRegistry.java:139)
>         at org.jboss.mx.server.MBeanServerImpl.removeNotificationListener(MBeanServerImpl.java:820)
>         at org.jboss.varia.scheduler.ScheduleManager$ScheduleInstance.stop(ScheduleManager.java:835)
>         at org.jboss.varia.scheduler.ScheduleManager.removeSchedule(ScheduleManager.java:325)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ...
> The problem can be demonstrated by uncommenting the single schedule provider example, then letting the schedule execute its 10 repetitions, then stop the server.
> By looking in the code ScheduleInstance.stop() is called twice:
> a) when a schedule has expired
> b) when the schedule provider deregisters.

-- 
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