APAR status
Closed as program error.
Error description
There is a memory leak and large object allocation
failures within the DRS component. This problem was identified
with the portal application running on WebSphere 5.1
Displays similar to the following object stack from the heapdump
generated.
879,707,488 [88] 9 com/ibm/disthub/impl/jms/TopicSubscriberImpl
0x4d534010
879,703,696 [536] 80
com/ibm/ws/webcontainer/httpsession/DRSHttpSessCache 0x4d484208
281,323,840 [56] 1 java/util/HashMap 0x4d48e748
231,555,592 [32] 1 java/util/LinkedList 0x4d48e160
122,459,592 [32] 1 java/util/LinkedList 0x4d48d4c0
105,056,312 [56] 1 java/util/HashMap 0x4d48dde8
92,160,056 [56] 1 java/util/HashMap 0x4d48e6c8
25,258,744 [56] 2 java/util/HashMap 0x4d48d1a8
10,817,784 [56] 1 java/util/HashMap 0x4d48d610
6,857,384 [56] 1 java/util/HashMap 0x4d48d2a8
3,944,616 [56] 1 java/util/HashMap 0x4d48d2d8
163,984 [32] 1 java/util/LinkedList 0x4d48e280
64,064 [32] 1 java/util/LinkedList 0x4d48df98
17,080 [56] 6 com/ibm/ws/drs/DRSJMS 0x4d48e108
10,328 [24] 1 com/ibm/ws/drs/DRSConstrainedList 0x4d48de48
2,824 [56] 1 java/util/HashMap 0x4d48d5e0
1,784 [56] 1 java/util/HashMap 0x4d434dd0
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server *
* using HTTP session memory to memory *
* replication. *
****************************************************************
* PROBLEM DESCRIPTION: Memory leak within the replication *
* service causes large object allocation *
* failures resulting in an OutOfMemory *
* exception. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
A memory leak within the replication service causes large
object allocation failures resulting in an OutOfMemory
exception. When the session manager does not find a requested
session in the cache, it sends a 'get' request to all partner
session managers to determine if the session is stored in
another WebSphere Application Server. If a large number (50+)
of 'get' requests are produced for sessions that do not exist,
then the replication service incorectly fills 1 of its tables
with non-existent entries. Subsequently, the table continues to
grow in the heap until it reaches an OutOfMemory exception.
Problem conclusion
When the 'get' request does not return a session object, the
entry is removed from the internal table. Additional changes
were made to increase the capacity of incoming requests that
the replcation service could manage.
This fix for this APAR is targeted for inclusion in fixpack
5.0.2.15 and 5.1.1.8. Please refer to the Recommended Updates
page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix Comments
APAR information |
APAR number |
PK13777 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
10I |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-10-20 |
Closed date |
2005-11-01 |
Last modified date |
2005-11-01 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
|
Fix information |
Fixed component name |
WAS BASE 5.0 |
Fixed component ID |
5630A3600 |
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 |
|