You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Bruce Snyder (JIRA)" <ji...@apache.org> on 2010/09/18 18:47:53 UTC
[jira] Updated: (AMQ-2295) Inconsistencies using browseMessages()
in JMX on a queue
[ https://issues.apache.org/activemq/browse/AMQ-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Snyder updated AMQ-2295:
------------------------------
Fix Version/s: 5.5.0
(was: 5.4.1)
> Inconsistencies using browseMessages() in JMX on a queue
> --------------------------------------------------------
>
> Key: AMQ-2295
> URL: https://issues.apache.org/activemq/browse/AMQ-2295
> Project: ActiveMQ
> Issue Type: Bug
> Components: JMX
> Affects Versions: 5.2.0
> Environment: centos 5, java 1.6.0_13, 32bit x86
> Reporter: David Schlenk
> Fix For: 5.5.0
>
>
> I'm trying to write a utility to monitor our JMS queues using JMX. I'm having a hard time getting all of the messages currently in queue to show up when I call the browseMessages operation. It seems to randomly stop keeping track of how many messages are actually in the queue after a period of time when no consumers are active on the queue. Once a consumer connects and starts consuming messages then the browse function seems to work OK again. I'm using this configuration for my persistence:
> <persistenceAdapter>
> <amqPersistenceAdapter syncOnWrite="false" directory="${activemq.base}/data" maxFileLength="20 mb"/>
> </persistenceAdapter>
> Messages come in via stomp (<transportConnector name="stomp+ssl" uri="stomp+ssl://localhost:1940) and are consumed via http (<transportConnector name="ihttp" uri="http://localhost:61618"/>).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.