You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Craig Condit (JIRA)" <ji...@apache.org> on 2011/01/25 23:41:45 UTC

[jira] Created: (AMQ-3159) Log file offset in addition to file location in checkpointUpdate()

Log file offset in addition to file location in checkpointUpdate()
------------------------------------------------------------------

                 Key: AMQ-3159
                 URL: https://issues.apache.org/jira/browse/AMQ-3159
             Project: ActiveMQ
          Issue Type: Improvement
          Components: Message Store
    Affects Versions: 5.4.2
         Environment: All
            Reporter: Craig Condit
            Priority: Trivial


We have been trying to troubleshoot issues with messages not being deleted from the KahaDB store, and have determined that in our case, it is often due to uncommitted transactions. MessageDatabase.checkpointUpdate() logs the location of the first open transaction, but not the filenumber. This patch logs both, to make finding the offending transaction easier.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (AMQ-3159) Log file offset in addition to file location in checkpointUpdate()

Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQ-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-3159.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 5.5.0
         Assignee: Gary Tully

patch applied in r063712

URL: http://svn.apache.org/viewvc?rev=1063712&view=rev

> Log file offset in addition to file location in checkpointUpdate()
> ------------------------------------------------------------------
>
>                 Key: AMQ-3159
>                 URL: https://issues.apache.org/jira/browse/AMQ-3159
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Message Store
>    Affects Versions: 5.4.2
>         Environment: All
>            Reporter: Craig Condit
>            Assignee: Gary Tully
>            Priority: Trivial
>             Fix For: 5.5.0
>
>         Attachments: log-location.patch
>
>
> We have been trying to troubleshoot issues with messages not being deleted from the KahaDB store, and have determined that in our case, it is often due to uncommitted transactions. MessageDatabase.checkpointUpdate() logs the location of the first open transaction, but not the filenumber. This patch logs both, to make finding the offending transaction easier.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (AMQ-3159) Log file offset in addition to file location in checkpointUpdate()

Posted by "Craig Condit (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQ-3159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Craig Condit updated AMQ-3159:
------------------------------

    Attachment: log-location.patch

Patch to MessageDatabase.java to implement change.

> Log file offset in addition to file location in checkpointUpdate()
> ------------------------------------------------------------------
>
>                 Key: AMQ-3159
>                 URL: https://issues.apache.org/jira/browse/AMQ-3159
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Message Store
>    Affects Versions: 5.4.2
>         Environment: All
>            Reporter: Craig Condit
>            Priority: Trivial
>         Attachments: log-location.patch
>
>
> We have been trying to troubleshoot issues with messages not being deleted from the KahaDB store, and have determined that in our case, it is often due to uncommitted transactions. MessageDatabase.checkpointUpdate() logs the location of the first open transaction, but not the filenumber. This patch logs both, to make finding the offending transaction easier.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.