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