[jboss-jira] [JBoss JIRA] (WFLY-10047) OOM caused by jgroups objects UNICAST3$SenderEntry#1

[Erich Duda (JIRA)]

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

Erich Duda commented on WFLY-10047:
-----------------------------------

Here is the start up configuration which was logged by the test. The servers should be bound to {{127.0.0.1}}.

{code}
INFO: Manual starting of a server instance with overridden configuration. New configuration: {managementAddress=127.0.0.1, adminOnly=false, javaVmArguments=-Xms64m -Xmx788m -XX:MaxPermSize=256m
                    -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000
                    -Dorg.jboss.byteman.transform.all
                    -Dsun.rmi.dgc.server.gcInterval=3600000
                    -javaagent:/home/hudson/hudson_workspace/workspace/early-testing-messaging-weekly-common-cluster/.repository/org/jboss/byteman/byteman/3.0.5/byteman-3.0.5.jar=prop:org.jboss.byteman.verbose=t
rue,address:127.0.0.1,port:9091
                    -Djboss.modules.system.pkgs=org.jboss.byteman -Xbootclasspath/a:/home/hudson/hudson_workspace/workspace/early-testing-messaging-weekly-common-cluster/.repository/org/jboss/byteman/byteman/3.0
.5/byteman-3.0.5.jar:/home/hudson/hudson_workspace/workspace/early-testing-messaging-weekly-common-cluster/.repository/org/jboss/byteman/byteman-submit/3.0.5/byteman-submit-3.0.5.jar
                    -Djboss.bind.address=127.0.0.1
                    -Djboss.bind.address.management=127.0.0.1
                    -Djboss.bind.address.unsecure=127.0.0.1
                    -Djboss.bind.address.private=127.0.0.1
                    -XX:+HeapDumpOnOutOfMemoryError
                    -Djava.net.preferIPv4Stack=true
                    -Djboss.modules.policy-permissions=true
                    -Djboss.node.name=node-1
                    -Dxnio.nio.selector.main=sun.nio.ch.DevPollSelectorImpl
                    
                 -Djboss.socket.binding.port-offset=0 -Djboss.messaging.group.address=237.47.146.238 -Djboss.default.multicast.address=237.47.146.238, password=minono532/20, startupTimeoutInSeconds=300, managementPort=9990, jbossHome=/home/hudson/hudson_workspace/workspace/early-testing-messaging-weekly-common-cluster/server1/jboss-eap, serverConfig=standalone-full-ha.xml, username=admin}
{code}

> OOM caused by jgroups objects UNICAST3$SenderEntry#1
> ----------------------------------------------------
>
>                 Key: WFLY-10047
>                 URL: https://issues.jboss.org/browse/WFLY-10047
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 13.0.0.Beta1
>            Reporter: Erich Duda
>            Assignee: Paul Ferraro
>            Priority: Blocker
>         Attachments: heapdump.png
>
>
> JGroups objects UNICAST3$SenderEntry#1 caused OOM on Wildfly server during the boot. See attached picture.  !heapdump.png|thumbnail! 
> *User impact:* If users use JGroups for clustering, the server may get OOM what can cause undefined behavior.
> The *blocker* priority was set, because this is regression against previous versions of Wildfly and the OOM is serious error which prevents server to work properly.
> The issue was hit in following scenario.
> # start two servers (nodes) in cluster with one queue
> # producer starts to send messages to queue to node-1
> # node-2 is killed and restarted during sending messages <---- *Here the test failed, when the node-2 was started after that it had been killed.*
> # start consumer on node-2 which reads messages from queue
> # servers are stopped
> The Wildfly was built from following source code:
> repo: https://github.com/jmesnil/wildfly
> branch: WFLY-9407_upgrade_artemis_2.5.0
> commit SHA: 06c878a313d3cad323889d017e60fd5533204d1a
> JGroups version: 4.0.10.Final



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)