You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2016/05/04 21:41:13 UTC

[jira] [Closed] (AMQ-6258) It is not possible to query KahaDB instances using ActiveMQ's javax.jms.QueueBrowser implementation

     [ https://issues.apache.org/jira/browse/AMQ-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-6258.
-----------------------------
    Resolution: Duplicate

This is working as designed.  You can alter the maxBrowsePageSize to allow for more paged in messages but there will be limits due to memory usage that must be considered.  


> It is not possible to query KahaDB instances using ActiveMQ's javax.jms.QueueBrowser implementation
> ---------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-6258
>                 URL: https://issues.apache.org/jira/browse/AMQ-6258
>             Project: ActiveMQ
>          Issue Type: Wish
>          Components: Broker, KahaDB
>    Affects Versions: NEEDS_REVIEW, 5.12.1
>            Reporter: Ben Nisbet
>
> Creating an unrestricted or selector constrained QueueBrowser does not return messages that are in the persistent store but not paged into memory.
> (i.e. only members of org.apache.activemq.broker.region.Queue.pagedInMessages can ultimately be queried) 
> Once the memory usage limit for a queue is reached no further messages can be paged in and this renders the remaining messages in KahaDB files opaque to QueueBrowser instances.
> Alternatively is there a KahaDB specific tool for querying messages in the log files directly?



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