Jgroups memory leak in jgroups-broadcast-group

[Davy Koravand]

Hi all, we noticed a memory leak in our application where the heap keeps increasing in size in WildFly 23. We found the cause to be the jgroups-broadcast-group, and removing the following configuration in the activemq subsystem also removes the leak:

<jgroups-broadcast-group name="bg-group1" jgroups-cluster="activemq-cluster" connectors="http-connector"/>

Here is a screenshot of the memory analyzer to to show which area it's in:

 

Looking a bit deeper we saw LinkedDequeNodes being created over time but not cleaned up, which slowly increased the heap.

Any idea what we could try here or what the root cause could be? The environments with this configuration crash weekly because of this.

[Paul Ferraro]

The configuration above causes messages to be periodically sent to all cluster members to be processed by a jgroups-discovery-group.  If no such discovery group exists, these messages will sit in a queue waiting to be read (which explains your observations).