[
https://issues.apache.org/jira/browse/AMQ-6014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15021022#comment-15021022
]
Christopher L. Shannon commented on AMQ-6014:
---------------------------------------------
[~gtully],
Looks like this fix is causing a test failure in this test:
org.apache.activemq.usecases.DurableSubscriberNonPersistentMessageTest.testDurableSubscriberNonPersistentMessage
It seems that the issue is the extra call node.incrementReferenceCount() in the
createMessageDispatch() method of DurableTopicSubscription is causing the
cursorMemoryUsage value checked in the test to no longer be 0. Not sure if
this is an actual regression or if the failing test just needs to be adjusted
for the new behavior that you added in this patch.
> 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)
