[jboss-jira] [JBoss JIRA] (JGRP-2040) Seeing a OOM in JGroup 3.4

[Bela Ban (JIRA)]

    [ https://issues.jboss.org/browse/JGRP-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198301#comment-13198301 ] 

Bela Ban commented on JGRP-2040:
--------------------------------

The code below is executed. Apparently, a sender sends an int of 1.6GB, so the question is who is connecting to this member. Can you do a {{netstat -na}} and then grep for the local port?

Note that the OOME is caught, so this should not have any adverse effects.

{code}
     public void run() {
            Throwable t=null;
            while(canRun()) {
                try {
                    int len=in.readInt();
                    if(buffer == null || buffer.length < len)
                        buffer=new byte[len];
                    in.readFully(buffer, 0, len);
                    updateLastAccessed();
                    server.receive(peer_addr, buffer, 0, len);
                }
                catch(OutOfMemoryError mem_ex) {
                    t=mem_ex;
                    break; // continue;
                }
                catch(IOException io_ex) {
                    t=io_ex;
                    break;
                }
                catch(Throwable e) {
                }
            }
{code}

> 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)