APAR status
Closed as program error.
Error description
LocalNotificationServiceDispatcher is creating small objects and
exhausting the Java heap. OutOfMemory Exception in
com.ibm.ws.util.Overflow class.
OutoFMemory will be thrown when events generated in the
WebSphere Application server environment is huge than normal.
At some point the file under wstemp\events will grow
beyond 1 MB and the situation is not handled properly.
DeploymentManager will throw heapdumps and javacore files.
From review of the heapdump the heap is exhausted by the 127
2,170,032 byte [byte] objects which are similar to the one
below:
3,203,088 [32] 1 java/util/ArrayList 0x325db328
3,203,056 [1,872] 463 array of java/lang/Object 0x32cafd98
2,170,032 [2,170,032] 0 byte[] 0x367e3ee8
The current thread in every javacore is responsible for
creating excessive number of ArrayList (ArrayList are root
object)
"LocalNotificationServiceDispatcher :
at com.ibm.ws.util.OverflowFile.refactor
at com.ibm.ws.util.OverflowFile.writeBytes
at com.ibm.ws.util.OverflowFile.refactor
at com.ibm.ws.util.OverflowFile.writeBytes
at com.ibm.ws.util.OverflowFile.refactor
at com.ibm.ws.util.OverflowFile.writeBytes
at com.ibm.ws.util.OverflowFile.refactores
at com.ibm.ws.util.OverflowFile.writeBytes
at com.ibm.ws.util.OverflowFile.refactor
at com.ibm.ws.util.OverflowFile.writeBytes
at com.ibm.ws.util.OverflowFile.refactor
at com.ibm.ws.util.OverflowFile.writeBytes
... (more frames not shown)
WebSphere Application Server
Javacore
HeapDump
OutOfMemory
Local fix
Restart Deploymentmanager
Problem summary
****************************************************************
* USERS AFFECTED: Websphere Application Server users with an *
* environment which has a lot of runtime *
* events generated. *
****************************************************************
* PROBLEM DESCRIPTION: The events generated during runtime *
* are written as .ser files under *
* wstemp folder. *
* The size limit of this file is 1 MB. *
* When the file size exceeds this limit *
* the contents are read back to *
* memory which is leading to large *
* objects being created in JVM heaps *
* and finally lead to OutOfMemory errors *
****************************************************************
* RECOMMENDATION: *
****************************************************************
The logic which handles the IO Operation during the time it is
trying to limit the size of the output file was incorrect. This
was leading to memory corruption - negative seek Offset errors
and core dumps.
Problem conclusion
The logic to handle the file size as it exceeds 1 MB was
rewritten .
The fix for this APAR is currently targeted for inclusion in
fixpack 5.0.2.13. and 5.1.1.7
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 |
PK07048 |
Reported component name |
WAS NETWRK DEPL |
Reported component ID |
5630A3601 |
Reported release |
00A |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2005-06-09 |
Closed date |
2005-08-02 |
Last modified date |
2005-08-02 |
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 NETWRK DEPL |
Fixed component ID |
5630A3601 |
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 |
|