PQ95803: FOR V4 DATASOUCE IF IDLE TIMEOUT IS SET TO 0, THE JAVAPROCESS CONSUMES HIGH CPU.

 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
Problem: For 40 datasouce if Idle timeout is set to 0, the
javaprocess consumes high CPU.
But, as per the document, setting this value to 0, should
disable Idle Timeout.
Local fix
Setting the High Value for the Idle Timeout
Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server users       *
*                 of v4 (JDBC) dataSources and connection      *
*                 pooling                                      *
****************************************************************
* PROBLEM DESCRIPTION: If the customer were to set the idle    *
*                      timeout to 0, which should disable it,  *
*                      they may see a system slowdown          *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
We had not guarded the IdleTimeout so that a zero value
would disable the timeout.  Instead, alarms were created
with a 0 time, so essentially an infinite number of alarms
started at the same time.
Problem conclusion
We added the guard so that setting IdleTimeout to 0
will disable it.
The fix for this APAR is currently targeted for inclusion
in fixpack 5.0.2.9 and 5.1.1.2. Please refer to the
Recommended Updates page for delivery dates:

http://www-1.ibm.com/support/docview.wss?rs=180
&context=SSEQTP&uid=swg27004980

For V4.0.7 this fix will be available via the next
cumulative cm Fix.
Temporary fix Comments
APAR information
APAR number PQ95803
Reported component name WAS NETWRK DEPL
Reported component ID 5630A3601
Reported release 10A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-10-15
Closed date 2004-11-15
Last modified date 2005-01-12

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
JDBC          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P 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: 10A
Software edition:
Reference #: PQ95803
IBM Group: Software Group
Modified date: Jan 12, 2005