Fixes are available
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
8.0.0.1: WebSphere Application Server V8.0 Fix Pack 1
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
8.0.0.2: WebSphere Application Server V8.0 Fix Pack 2
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
APAR status
Closed as program error.
Error description
OutOfMemory occurs during bootstrap when fully populated session data is being propagated to a newly joined application server. The OutOfMemoryError occurs in DRSByteArrayPoolSet.getByteArray, but the key stack frame is DRSSolicitor.handleSolicitEntryRequest. For example: at com/ibm/ws/drs/pool/DRSByteArrayPoolSet.getByteArray(DRSByteArra yPoolSet.java:168(Compiled Code)) at com/ibm/ws/drs/message/DRSByteStream.growByteArray(DRSByteStream .java:309(Compiled Code)) at com/ibm/ws/drs/message/DRSByteStream.write(DRSByteStream.java:16 5(Compiled Code)) at java/io/ObjectOutputStream$BlockDataOutputStream.write(ObjectOut putStream.java:1822(Compiled Code)) at java/io/ObjectOutputStream.write(ObjectOutputStream.java(Compile d Code)) ... at com/ibm/ws/drs/message/DRSBuffWrapper.storeObject(DRSBuffWrapper .java:169(Compiled Code)) at com/ibm/ws/drs/message/DRSMessageHelper.getSerializedForm(DRSMes sageHelper.java:179(Compiled Code)) at com/ibm/ws/drs/managers/DRSSolicitor.handleSolicitEntryRequest(D RSSolicitor.java:345) at com/ibm/ws/drs/stack/DRSClientCallback.processRcvMessage(DRSClie ntCallback.java:346(Compiled Code)) at com/ibm/ws/drs/stack/DRSStack.processRcvMessage(DRSStack.java:29 5(Compiled Code)) at com/ibm/ws/drs/DRSDomain.messageReceived(DRSDomain.java:614(Comp iled Code)) ...
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server using HTTP session memory to memory * * replication. * **************************************************************** * PROBLEM DESCRIPTION: An out of memory can occur when an * * application server joins an * * established, fully populated * * replication domain. * **************************************************************** * RECOMMENDATION: * **************************************************************** The existing application servers will attempt to replicate HTTP session data to the application server that is joining the replication domain. The Data Replication Service (DRS) attempts to send the entire collection of HTTP session data in one large message. Serializing the large message can result in an out of memory condition.
Problem conclusion
The DRS service will replicate HTTP session data in multiple batches of 50 objects in each batch. A JVM custom property is being introduced to set the batch size, DRS_BATCH_INTERVAL_SIZE. The default is 50. To set a JVM custom property: From the administrative console: Click Servers > Application Servers > server > Java and Process Management > Process Definition > Java Virtual Machine > Custom Properties. Create a new custom property, if required, by clicking New, then add DRS_BATCH_INTERVAL_SIZE in the name field and a positive integer in the value field. The fix for this APAR is currently targeted for inclusion in fix packs 6.1.0.41, 7.0.0.19 and 8.0.0.1. 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
PM38550
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-05-05
Closed date
2011-06-29
Last modified date
2011-06-29
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP
R800 PSY
UP
Document Information
Modified date:
27 October 2021