activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6014) Offline Durable Topic Subscription exceeds memory limits
Date Tue, 05 Jan 2016 15:08:40 GMT

    [ https://issues.apache.org/jira/browse/AMQ-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15083198#comment-15083198
] 

ASF subversion and git services commented on AMQ-6014:
------------------------------------------------------

Commit 26665fa1b98a9004fc90a6eeea26ca06eb53d118 in activemq's branch refs/heads/activemq-5.13.x
from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=26665fa ]

https://issues.apache.org/jira/browse/AMQ-6094 - regression via https://issues.apache.org/jira/browse/AMQ-6014
- incorrect ref count on message expiry event during cursor move for dispatch. Fix and test
- thanks for the test

(cherry picked from commit e3df09b9db09d6cf2834b0beb901c253be9b6120)


> Offline Durable Topic Subscription exceeds memory limits
> --------------------------------------------------------
>
>                 Key: AMQ-6014
>                 URL: https://issues.apache.org/jira/browse/AMQ-6014
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.12.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.13.0, 5.12.2
>
>
> To reproduce:
> 1) Start two durable subscriptions using the openwire swissarmy examples:
> ant consumer -Dtopic=true -Ddurable=true -Dsubject=test -Duser=admin -Dpassword=admin
-Dmax 500000
> ant consumer -Dtopic=true -Ddurable=true -Dsubject=test -Duser=admin -Dpassword=admin
-DclientId=c2
> 2) Start a producer using the following command:
> ant producer -Dtopic=true -Ddurable=true -Dsubject=test -Duser=admin -Dpassword=admin
-Dmax=500000
> 3) Kill one of the durable topic subscribers and let the test run
> 4) the broker will go OOM
> The cache for the offline durable sub is not recording is cached messages against system
memory usage as it should. Hence the limits are not hit.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message