PQ93259: WAS 5.0.2.7 JMX Timer not firing reliably.

 Fixes are available

5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux



APAR status
Closed as program error.

Error description
JMX timer not firing reliably. For Example: If Timer A is set
for 10 minutes and then timer B is set for 2 minutes. Timer B
will not fire until Timer A has fired already.
Local fix
Gautam Pamu from Tivoli has supplied two files viz.,
RunnableTimer.class and Timer.class which fix the problem. They
need to be incorporated into the
\Websphere\Appserver\lib\jmxc.jar file for the WAS 5.0.2.8
build.

CIBM Parter has this urgent requirement and would like to
commit to their customer that this fix will be available in WAS
5.0.2.8.

08/25 --11:30 AM - We are waiting on customer to get back to us
on the status of the fix.

- If customer responds with a positive then Gautam Pamu will
supply the officials files to be incorporated into WAS jmxc.jar
library.

At that point I will forward this APAR/PMR and the files to the
right entity to put the files in the build.
Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server users who make  *
*                 use of the timer mbeans.                     *
****************************************************************
* PROBLEM DESCRIPTION: JMX timer beans are not firing          *
*                      properly.Consider the case of firing    *
*                      2 timers A and B with firing interval   *
*                      60 and 10.                              *
*                      In this case it is sending              *
*                      notification for B but it is sending    *
*                      after 60 sec and all the                *
*                      notifications of B are fired at the     *
*                      same time.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Changes were done to jmxc.jar to take care of this issue.
Problem conclusion
Changes were done to jmxc.jar to take care of this issue.
Temporary fix Comments
APAR information
APAR number PQ93259
Reported component name WAS BASE 5.0
Reported component ID 5630A3600
Reported release 00A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-08-24
Closed date 2004-10-27
Last modified date 2004-10-27

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
TMX4J          

Publications Referenced

Fix information

Applicable component levels
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00S PSY    UP
R00W PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ93259
IBM Group: Software Group
Modified date: Oct 27, 2004