[jira] [Work logged] (AMQ-7118) KahaDB store limit can be exceeded with durable subscribers.

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

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

ASF GitHub Bot logged work on AMQ-7118:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 18/Oct/19 18:49
            Start Date: 18/Oct/19 18:49
    Worklog Time Spent: 10m 
      Work Description: jbonofre commented on issue #326: AMQ-7118: fix issue with the unchanged acknowledgement map.
URL: https://github.com/apache/activemq/pull/326#issuecomment-543885060
 
 
   It has been already applied.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 330717)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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 Mark Goodyear
>            Priority: Critical
>             Fix For: 5.16.0, 5.15.8
>
>         Attachments: kahaCommands.jpg
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)