APAR status
Closed as program error.
Error description
Java throws an OutOfMemory error when federation of a node is done using addNode.sh script in a WAS environment. The stack trace looks like this: JVMST105: Unable to allocate an array object, Array element exceedes IBM JDK limit of 268435455 elements Exception in thread "main" java.lang.OutOfMemoryError: JVMCI156:OutOfMemoryError, IBMJVM_ResizeArray - stAllocArray for new array failed at com.ibm.jvm.ExtendedSystem.resizeArray at java.io.ByteArrayOutputStream.write at sun.net.www.http.PosterOutputStream.write at java.io.DataOutputStream.write at java.util.zip.DeflaterOutputStream.deflate at java.util.zip.DeflaterOutputStream.write at java.util.zip.GZIPOutputStream.write
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: WebSphere Application Server version 6.02 * * users * **************************************************************** * PROBLEM DESCRIPTION: OutofMemory error using AddNode.sh to * * federate a node * **************************************************************** * RECOMMENDATION: * **************************************************************** Java program throws an OutOfMemory error when federation of a node is done using addNode.sh script in the WebSphere Application Server environment. The stack trace looks like this: JVMST105: Unable to allocate an array object, Array element exceedes IBM JDK limit of 268435455 elements Exception in thread "main" java.lang.OutOfMemoryError: JVMCI156:OutOfMemoryError, IBMJVM_ResizeArray - stAllocArray for new array failed at com.ibm.jvm.ExtendedSystem.resizeArray at java.io.ByteArrayOutputStream.write at sun.net.www.http.PosterOutputStream.write at java.io.DataOutputStream.write at java.util.zip.DeflaterOutputStream.deflate at java.util.zip.DeflaterOutputStream.write at java.util.zip.GZIPOutputStream.write
Problem conclusion
addNode operation with the includeapps option performs transfer of application files that have very large EAR files of size of almost running into 150MB being deployed. This happens due to improper algorithm in ByteArrayOutputStream that doubles the size of the allocation request and sends the request down to the JVM. The size after the doubling, will be greater than 256MB in size and a byte array of size greater than 256MB is not supported on a 1.4.2 32-bit JVM. . To obtain the fix: - Install build 20051108 or later - Upgrade WebSphere 5.1.x to 5.1.1.8 when available. - Upgrade WebSphere Application Server 6.0.X to 6.0.2.5 when available.
Temporary fix
Comments
APAR Information
APAR number
PK15242
Reported component name
WEBSPH APP SERV
Reported component ID
5724J0800
Reported release
60A
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2005-11-15
Closed date
2005-11-15
Last modified date
2006-02-22
APAR is sysrouted FROM one or more of the following:
PK14592
APAR is sysrouted TO one or more of the following:
Modules/Macros
JDK
Fix information
Fixed component name
WEBSPH APP SERV
Fixed component ID
5724J0800
Applicable component levels
R60A PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
10 February 2022