You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2012/10/05 17:06:02 UTC

[jira] [Created] (AMQ-4094) offline durable subs with selectors can lead to page leaks in the index and bloat of db.data in kahadb

Gary Tully created AMQ-4094:
-------------------------------

             Summary: offline durable subs with selectors can lead to page leaks in the index and bloat of db.data in kahadb
                 Key: AMQ-4094
                 URL: https://issues.apache.org/jira/browse/AMQ-4094
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.6.0, 5.7.0
            Reporter: Gary Tully
             Fix For: 5.8.0


There is a page leak in the index, related to durable subs with selectors. producing and consuming past variable limits demonstrate incremental growth in the db.data, the in-use page count increases

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (AMQ-4094) offline durable subs with selectors can lead to page leaks in the index and bloat of db.data in kahadb

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

Gary Tully commented on AMQ-4094:
---------------------------------

a workaround is to avoid page overflow by configuring a large index page size for kahadb. The size needs to be > any single stored value. In the case of offline durables with selectors the sequence set of pending messages needs to fit in one page.
                
> offline durable subs with selectors can lead to page leaks in the index and bloat of db.data in kahadb
> ------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-4094
>                 URL: https://issues.apache.org/jira/browse/AMQ-4094
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.6.0, 5.7.0
>            Reporter: Gary Tully
>              Labels: db.data, durable, kahadb, topic
>             Fix For: 5.8.0
>
>
> There is a page leak in the index, related to durable subs with selectors. producing and consuming past variable limits demonstrate incremental growth in the db.data, the in-use page count increases

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (AMQ-4094) offline durable subs with selectors can lead to page leaks in the index and bloat of db.data in kahadb

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

Gary Tully resolved AMQ-4094.
-----------------------------

    Resolution: Fixed
      Assignee: Gary Tully

fix in http://svn.apache.org/viewvc?rev=1394733&view=rev
                
> offline durable subs with selectors can lead to page leaks in the index and bloat of db.data in kahadb
> ------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-4094
>                 URL: https://issues.apache.org/jira/browse/AMQ-4094
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.6.0, 5.7.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: db.data, durable, kahadb, topic
>             Fix For: 5.8.0
>
>
> There is a page leak in the index, related to durable subs with selectors. producing and consuming past variable limits demonstrate incremental growth in the db.data, the in-use page count increases

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira