[
https://issues.jboss.org/browse/JGRP-2040?page=com.atlassian.jira.plugin....
]
Bela Ban commented on JGRP-2040:
--------------------------------
Apparently, the receiver is reading an int which should be the length of the following
buffer, but the data it is reading doesn't have an int. Is some other process sending
data to the JGroups process? This could lead to TCP interpreting random data as an int
(which is way to large).
Seeing a OOM in JGroup 3.4
--------------------------
Key: JGRP-2040
URL:
https://issues.jboss.org/browse/JGRP-2040
Project: JGroups
Issue Type: Bug
Affects Versions: 3.4
Environment: Linux Operating System
Reporter: Kshitiz Saxena
Assignee: Bela Ban
We are seeing an OOM in our application where thread dump points to JGroup.
We see the below in thread dumps,
3XEHSTTYPE 07:33:24:346241000 GMT j9vm.294 - >setCurrentException index=11
constructorIndex=0 detailMessage=0000000000F61678
3XEHSTTYPE 07:33:24:346183000 GMT j9mm.126 - at 0000000050F8CD60
java/lang/Thread.run()V, jit 00007FCF323EA580, pc 00007FCF489E0A36
3XEHSTTYPE 07:33:24:346179000 GMT j9mm.126 - at 0000000053644748
*org/jgroups/blocks/TCPConnectionMap$TCPConnection$Receiver.run()*V, jit 0000000000000000,
pc 00007FCF3354D334
3XEHSTTYPE 07:33:24:346175000 GMT j9mm.101 - J9AllocateIndexableObject() returning
NULL! *1650814064 bytes* requested for object of class 0000000050F79700 from memory space
'Generational' id=00007FCF440427C0
In the thread dump we also see
WARNING : OutOfMemoryError possibly caused by 1650814064 bytes requested for object of
class 0000000050F79700 from memory space 'Generational' id=00007FCF440427C0
Java Heap Information
-Xmx (Maximum Java heap size) : 1280m
-Xms (Initial Java heap size) : 640m
-Xss (Maximum stack size for Java threads) : 256k
Total Java heap size: 1.25 GB
Used Java heap size: 174.27 MB
Free Java heap size: 1.08 GB
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)