Re: JMX Console and deleted messages

I'm seeing the exact behaviour described below with ActiveMQ 5.3. Using the JMX MBean, I purge a queue that contains 100 persistent messages. The statistics are updated to indicate the 100 dequeue and resulting 0 queue size. However, browseAsTable[] still shows all 100 messages. There was no

Purged messages still appear in JMX browseAsTable

I have a test case in ActiveMQ 5.3 that is failing and would like to know if this is expected behaviour or a bug. Here's the test: 1) Create 100 test messages in a queue 2) Use jconsole and verify that the queue size is 100 3) Use jconsole and browseAsTable() to view the messages 4) Use jconsole

Re: Purged messages still appear in JMX browseAsTable

Just a quick followup, I looked into org.apache.activemq.broker.region.Queue to see where the supposedly deleted messages were coming from and they're being picked up from the pagedInPendingDispatch list during doBrowse(...): // Messages that are paged in but have not yet been targeted at a

Problem with Virtual Topics and noLocal=true consumers

Hi, Suppose we have store-and-forward network of two brokers (A and B) that share a topic (T1). Each broker has a single consumer for T1 (ConsumerA and ConsumerB). A and B communicate by producing and consuming messages from T1. Since ConsumerA does not want to consume the messages that it

Re: How to maintain an historical view of queue contents?

Joe Fernandez wrote: Sounds like you're wanting to implement a message-level audit trail? With Camel, you could very quickly implement a wiretap message pattern (http://camel.apache.org/wire-tap.html) and have the wiretap route the tapped messages to a log4j appender. The appender's

Observing messages passing through a queue

Hello, I have an architecture in which one or more message producers place messages in a shared queue and a consumer pool processes the messages. While I can use JMX to monitor the number of messages produced and consumed, the messages are consumed so fast that I often can't browse them with

Observing messages passing through a queue

Hello, I have an architecture in which one or more message producers place messages in a shared queue and a consumer pool processes the messages. While I can use JMX to monitor the number of messages produced and consumed, the messages are consumed so fast that I often can't browse them with

Advice on creating a historical view of a queue's contents

Hello, I have an architecture in which one or more message producers place messages in a shared queue and a consumer pool processes the messages. While I can use JMX to monitor the number of messages produced and consumed, the messages are consumed so fast that I often can't browse them with

Advice on creating a historical view of a queue's contents

Hello, I have an architecture in which one or more message producers place messages in a shared queue and a consumer pool processes the messages. While I can use JMX to monitor the number of messages produced and consumed, the messages are consumed so fast that I often can't browse them with

Advice on creating a historical view of a queue's contents

Hello, I have an architecture in which one or more message producers place messages in a shared queue and a consumer pool processes the messages. While I can use JMX to monitor the number of messages produced and consumed, the messages are consumed so fast that I often can't browse them with

How to create an historical view of a queue

Hello, I have an architecture in which one or more message producers place messages in a shared queue and a consumer pool processes the messages. While I can use JMX to monitor the number of messages produced and consumed, the messages are consumed so fast that I often can't browse them with

How to maintain an historical view of queue contents?

Hello, I have an architecture in which one or more message producers place messages in a shared queue and a consumer pool processes the messages. While I can use JMX to monitor the number of messages produced and consumed, the messages are consumed so fast that I often can't browse them with

Unable to start ActiveMQ after blue screen of death

Hi, Yesterday, a system running ActiveMQ (queues only, no topics or durable subscribers) backed by the Kaha persistence store blue screened and on restart, ActiveMQ failed with the following stacktrace: java.io.EOFException at java.io.RandomAccessFile.readFully(Unknown Source)

When is it safe to close a consumer?

Hello, I have a test case that's currently failing with ActiveMQ 5.0.0 and 5.1-SNAPSHOT, and I want to confirm the proper behaviour before I file a JIRA ticket. My test involves creating a queue that contains a single queue. Two consumers within separate sessions attempt to read from the queue

Re: When is it safe to close a consumer?

My original message has a typo. The test involves create a single queue with a single *message*. -- View this message in context: http://www.nabble.com/When-is-it-%22safe%22-to-close-a-consumer--tp15749587s2354p15749606.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Is it ever OK to use a session *synchronously* from more than one thread?

Hello, The JavaDoc for ActiveMQSession states that it is a single-threaded class. Mr. Strachan re-iterates in this message about ensuring that each thread has its own session and producers/consumers: