[
https://issues.apache.org/jira/browse/AMQ-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15022037#comment-15022037
]
Gary Tully commented on AMQ-6014:
---------------------------------
[~cshannon] thanks for the heads up. that test was in a browser tab on the todo
list but was not getting the priority it deserved. It is indeed a regression. I
added a comment at the time and I think it was on the money, the cursor should
take ownership of the reference.
> 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)
