You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2016/07/14 13:19:20 UTC

[jira] [Created] (AMQ-6356) Processing a KahaUpdateMessageCommand can lead to wrong store size being reported

Christopher L. Shannon created AMQ-6356:
-------------------------------------------

             Summary: Processing a KahaUpdateMessageCommand can lead to wrong store size being reported 
                 Key: AMQ-6356
                 URL: https://issues.apache.org/jira/browse/AMQ-6356
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker, KahaDB
    Affects Versions: 5.13.3
            Reporter: Christopher L. Shannon
            Assignee: Christopher L. Shannon
            Priority: Minor


When KahaDB processes a KahaUpdateMessageCommand it's possible for the size statistic to be inadvertently increased in size.  This can happen if the location in the journal of the message command matches the new location.  This bug won't show up in normal usage as typically an update message command is only processed when a new command is written to the journal (and hence a new location) but should still be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)