activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darius Schier (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-3604) Garbage Collection does not work if mirroredQueue active -> OOM
Date Wed, 23 Nov 2011 09:33:39 GMT

     [ https://issues.apache.org/jira/browse/AMQ-3604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Darius Schier updated AMQ-3604:
-------------------------------

    Description: 
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.

{code:xml}
<destinationInterceptors>
  <mirroredQueue copyMessage = "true" postfix=".qmirror" prefix=""/>
</destinationInterceptors>
<destinationPolicy>
  <policyMap>
    <policyEntries>
      <policyEntry topic="testQueue.>" producerFlowControl="false" memoryLimit="1 mb"
optimizedDispatch="true"></policyEntry>
      <policyEntry queue="testQueue.>" producerFlowControl="false" memoryLimit="1 mb"
optimizedDispatch="true"></policyEntry>
    </policyEntries>
  </policyMap>
</destinationPolicy>

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

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

{code}

  was:
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.

{code:xml}
<destinationInterceptors>
  <mirroredQueue copyMessage = "true" postfix=".qmirror" prefix=""/>
</destinationInterceptors>
<destinationPolicy>
  <policyMap>
    <policyEntries>
      <policyEntry topic="testQueue.>" producerFlowControl="false" memoryLimit="1 mb"
optimizedDispatch="true"></policyEntry>
      <policyEntry queue="testQueue.>" producerFlowControl="false" memoryLimit="1 mb"
optimizedDispatch="true"></policyEntry>
    </policyEntries>
  </policyMap>
</destinationPolicy>

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

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

{code}

        Summary: Garbage Collection does not work if mirroredQueue active -> OOM  (was:
Garbage Collection does not work if mirroredQueue active)
    
> Garbage Collection does not work if mirroredQueue active -> OOM
> ---------------------------------------------------------------
>
>                 Key: AMQ-3604
>                 URL: https://issues.apache.org/jira/browse/AMQ-3604
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.0
>         Environment: Linux, Windows
> Java6
>            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.
> {code:xml}
> <destinationInterceptors>
>   <mirroredQueue copyMessage = "true" postfix=".qmirror" prefix=""/>
> </destinationInterceptors>
> <destinationPolicy>
>   <policyMap>
>     <policyEntries>
>       <policyEntry topic="testQueue.>" producerFlowControl="false" memoryLimit="1
mb" optimizedDispatch="true"></policyEntry>
>       <policyEntry queue="testQueue.>" producerFlowControl="false" memoryLimit="1
mb" optimizedDispatch="true"></policyEntry>
>     </policyEntries>
>   </policyMap>
> </destinationPolicy>
> <persistenceAdapter>
>   <kahaDB directory="${activemq.base}/data/kahadb"/>
> </persistenceAdapter>
> <systemUsage>
>   <systemUsage>
>     <memoryUsage>
>       <memoryUsage limit="10 mb"/>
>     </memoryUsage>
>     <storeUsage>
>       <storeUsage limit="10 gb"/>
>     </storeUsage>
>     <tempUsage>
>       <tempUsage limit="10 mb"/>
>     </tempUsage>
>   </systemUsage>
> </systemUsage>
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message