| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Out of memory error - java heap dump created |
« View previous topic :: View next topic » |
| Author |
Message
|
| geethgubi |
 Posted: Wed Oct 28, 2009 5:14 am Post subject: Out of memory error - java heap dump created |
 |
|
Apprentice
Joined: 18 Dec 2008
Posts: 44
|
Yesterday we got an abend file created for one of our EGs. When I analysed that file I came to know that abend file was created for outofmemory error. I took the java heap dump file and ran it through IBM support assistant tool using Memory dump analyser. But I got the output as below. I am sure this is because of the JMS input node with in my flow in the EG. I have only one flow running in that EG. But my question is how can I find why suddenly out of memory issue is raised. what would be the root cause of that issue? Can some one help me out for this issue?
| Code: |
...
-
java/util/Hashtable$HashtableCacheHashEntry@0x706e9f90:: Reach Size 44,409,236
-
java/util/Hashtable$HashtableCacheHashEntry@0x7068f320:: Reach Size 44,409,016
-
com/ibm/broker/jmsclientnodes/JMSClientOutputNode-static-@0x36406cc0:: Reach Size 44,408,984
-
com/ibm/broker/plugin/MbNode-static-@0x34ed4840:: Reach Size 44,407,216
-
com/ibm/broker/plugin/MbStackTraceParser-static-@0x3310e328:: Reach Size 44,347,866
-
com/ibm/broker/trace/Trace-static-@0x334333f0:: Reach Size 44,347,810
-
java/util/Vector@0x70094338:: Reach Size 44,346,360
-
java/lang/Object[ ]@0x70094358:: Reach Size 44,346,344
-
com/ibm/broker/server/Broker@0x70210948:: Reach Size 44,346,336
-
com/ibm/disthub2/impl/server/MessageProcessor@0x703e31a0:: Reach Size 44,339,609
-
com/ibm/disthub2/impl/multi/server/SSConnMgr@0x704c1700:: Reach Size 44,339,605
-
com/ibm/disthub2/impl/multi/server/SSConnMonitor@0x70500d98:: Reach Size 44,320,829
-
java/lang/ThreadGroup@0x70000388:: Reach Size 44,320,481
-
java/lang/Thread[ ]@0x7b304a00:: Reach Size 44,318,415
-
java/lang/Thread@0x7027a8e8:: Reach Size 37,077,166
-
org/apache/activemq/transport/tcp/TcpTransport@0x70274420:: Reach Size 37,076,902
-
org/apache/activemq/transport/WireFormatNegotiator@0x70274648:: Reach Size 37,056,109
-
org/apache/activemq/transport/MutexTransport@0x702746d8:: Reach Size 37,055,997
-
org/apache/activemq/transport/ResponseCorrelator@0x70274700:: Reach Size 37,055,985
-
org/apache/activemq/ActiveMQConnection@0x702747b0:: Reach Size 37,055,817
-
org/apache/activemq/management/JMSStatsImpl@0x702729d0:: Reach Size 37,052,021
-
java/util/concurrent/CopyOnWriteArrayList@0x70272a88:: Reach Size 37,051,941
*
java/lang/Object[ ]@0x7fff9010:: Reach Size 37,051,937 |
|
|
| Back to top |
|
 |
| AkankshA |
| Posted: Thu Oct 29, 2009 2:53 am Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
which vesrion of WMB are you running ??
is it possible for you to brief the processing of the flow which caused abend file and also can u paste the abend file here..
what errors does the system logs show ?
_________________
Cheers |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Thu Oct 29, 2009 3:47 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
From the information available its hard to determine whats the cause of this OutOfMemory error, however these are some quick thoughts:
Processing large messages can easily cause OutOfMemory issues if care is not taken.
Does the process size gradually increase over time or did it suddenly increase until it failed with the error below?
An IBMer might be able to comment on whether the size of the HashtableCacheHashEntry is large or as expected which may be indicative of a leak. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
