activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darius Schier (Created) (JIRA)" <>
Subject [jira] [Created] (AMQ-3604) Garbage Collection does not work if mirroredQueue active
Date Wed, 23 Nov 2011 09:29:40 GMT
Garbage Collection does not work if mirroredQueue active

                 Key: AMQ-3604
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker
    Affects Versions: 5.5.0
         Environment: Linux, Windows
            Reporter: Darius Schier
            Priority: Critical

We use mirroredQueues a lot.
If the feature is active (see configuration), we found out that dynamically created Queues
would lead to an OutOfMemory.
The Broker works fine
- if no mirroredQueue is defined in the configuration OR
- for queues that were available at startup of the broker (even if mirroredQueue is configured).

It crashes if a previously not available queue is created and filled with 'big' chunks of
data (e.g. 40k TextMessage).

The problem seems pretty close to AMQ-3157. We tried the snapshot without success.

  <mirroredQueue copyMessage = "true" postfix=".qmirror" prefix=""/>
      <policyEntry topic="testQueue.>" producerFlowControl="false" memoryLimit="1 mb"
      <policyEntry queue="testQueue.>" producerFlowControl="false" memoryLimit="1 mb"

  <kahaDB directory="${activemq.base}/data/kahadb"/>

      <memoryUsage limit="10 mb"/>
      <storeUsage limit="10 gb"/>
      <tempUsage limit="10 mb"/>


This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message