[
https://issues.apache.org/jira/browse/AMQ-7118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16706373#comment-16706373
]
ASF GitHub Bot commented on AMQ-7118:
-------------------------------------
GitHub user heathkesler opened a pull request:
https://github.com/apache/activemq/pull/327
AMQ-7118: fix issue where the ackMessageFileMapLocation gets written on
every checkpoint
fix issue where the ackMessageFileMapLocation gets written on every
checkpoint, even if it hasnt changed and include the use of the Atomic boolean.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/heathkesler/activemq AMQ7118-map
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq/pull/327.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #327
----
commit 5c08df663de650870d4e4b3f940d7838af96d188
Author: hkesler <hkesler@...>
Date: 2018-12-02T16:17:40Z
AMQ-7118: fix issue where the ackMessageFileMapLocation gets written on
every checkpoint, even if it hasnt changed and include the use of the Atomic
boolean
----
> 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 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)
