activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dejan Bosanac (JIRA)" <>
Subject [jira] Updated: (AMQ-2448) Memory leak when there are network connector retries to an unavailable broker
Date Thu, 06 May 2010 06:46:37 GMT


Dejan Bosanac updated AMQ-2448:

    Fix Version/s: 5.4.0
                       (was: 5.3.1)

> Memory leak when there are network connector retries to an unavailable broker
> -----------------------------------------------------------------------------
>                 Key: AMQ-2448
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.3.0
>         Environment: Debian Linux 5.0 amd64 with included Sun Java 6 JRE
>            Reporter: Alexander Fisher
>            Assignee: Gary Tully
>             Fix For: 5.4.0
>         Attachments: activemq1.xml, activemq2.xml, activemq3.xml, activemq4.xml, AMQ-2448.workingVMtest.patch
> I've discovered a reproducible memory leak.  After discussion on IRC, it is believed
to be related to my network of brokers configuration.
> I have a total of 4 brokers configured on 4 hosts (activemq1,2,3,4).
> activemq1 and activemq2 are a shared filesystem master slave pair.  activemq3 and activemq4
are setup in a similar way as a master/slave pair.
> Only one of activemq1 and 2 will be active at a time, likewise only one of activemq3
and 4.
> Both activemq1 and activemq2 have a config with the following networkConnector.
> <networkConnectors>
>                 <networkConnector
>                         uri="static://(tcp://activemq3:61616,tcp://activemq4:61616)"
>                         name="Connection to 3 and 4"
>                         networkTTL="5"
>                         dynamicOnly="true"/>
> </networkConnectors>
> The broker will only be able to connect to either 3 or 4 as only one can be running at
a time.
> For obvious reasons, connecting to the slave will fail, but the connection attempt will
be retried every 30 seconds by default (more often on initial startup due to backoff algorithm).
> It is believed that the continuous reconnect attempts are the source of the memory leak.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message