[jboss-jira] [JBoss JIRA] Closed: (JBAS-3282) ScheduleManager MBean uses fixed-rate execution on Java 1.4 and fixed-delay execution on Java 5.0
[ http://jira.jboss.com/jira/browse/JBAS-3282?page=all ]
Dimitris Andreadis closed JBAS-3282.
------------------------------------
Fix Version/s: JBossAS-5.0.0.Beta
Resolution: Done
Schedule & SchedulerManager mbeans now have a FixedRate attribute which is false by
default to match the default JMX Timer scheduling behaviour of FixedDelay execution as of
JDK5 or JBoss v4.0.5.
However, in the example configurations of:
deploy/scheduler-service.xml
deploy/schedule-manager-service.xml
The default is overriden using FixedRate==true to match the expected behaviour of the
jboss 4.x Timer, over jdk1.4 (which is FixedRate).
ScheduleManager MBean uses fixed-rate execution on Java 1.4 and
fixed-delay execution on Java 5.0
-------------------------------------------------------------------------------------------------
Key: JBAS-3282
URL: http://jira.jboss.com/jira/browse/JBAS-3282
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Scheduling/Timers
Affects Versions: JBossAS-4.0.4.GA
Reporter: Darran Lofthouse
Assigned To: Dimitris Andreadis
Priority: Critical
Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1
The ScheduleManager MBean uses fixed-rate execution on Java 1.4 and fixed-delay execution
on Java 5.0
The reason for this is because the ScheduleManager makes use of the
javax.management.timer.Timer class, when running with Java 1.4 we use our implementation
of the timer but when running with Java 5.0 we use the JRE implementation.
To get fixed-rate execution (which has been our default till Java 5.0) the
ScheduleManager should be using the method addNotification(String, String, Object, Date,
long, long, boolean) with the final boolean set to true.
We should possibly make the decision to use fixed-delay or fixed-rate configurable incase
people are already expecting fixed-dalay with Java 5.0.
--
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