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

Gary Tully commented on AMQ-7118:
---------------------------------

[~heathkesler] verify that the logic around 
https://github.com/apache/activemq/blob/master/activemq-kahadb-store/src/main/java/org/apache/activemq/store/kahadb/MessageDatabase.java#L1916
 still holds. 
That code is tracking modifications to trigger a checkpoint that expects that 
map to be unconditionally stored.

small note; very often the xml config is not necessary (the broker can be 
programmatically configure)  and the use of 61616 port can be avoided in favour 
of the vm transport. It makes the unit test tidier and more self contained and 
could lead to them being run in parallel. 
In any event, it is great to see a matching test that will protect this change.
.

> KahaDB store limit can be exceeded with durable subscribers.
> ------------------------------------------------------------
>
>                 Key: AMQ-7118
>                 URL: https://issues.apache.org/jira/browse/AMQ-7118
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: KahaDB
>    Affects Versions: 5.16.0, 5.15.8
>         Environment: JDK 8
>            Reporter: Jamie goodyear
>            Priority: Critical
>             Fix For: 5.15.8
>
>         Attachments: kahaCommands.jpg
>
>
> KahaDB store limit can be exceeded with durable subscribers.
> AMQ with store limit set, we can observe that the usage continues to increase 
> AFTER PFC is engaged. Given time, this growth stabilizes. The issue of having 
> exceeded the store limit remains.
> See below output from KahaDB dump in attachments:
> This appears to be caused by checkpointAckMessageFileMap. The log files are 
> not GC'd, and the KAHA_ACK_MESSAGE_FILE_MAP_COMMAND is replicated and the DB 
> log files continue to expand - this can become exponential. Side effect of 
> also not checking storage size in checkpoint update can cause the DB log 
> files to exceed any set limits. The real critical part is the duplicated and 
> leaking Kaha messages which appears to happen with durable subscribers.
>  
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to