org.apache.activemq.broker.TransportConnection - The connection to 'vm://activemqbroker#0' is taking a long time to shutdown.

Hi, We come across below message very often when we shutdown activemq where activemqbroker is the name we gave to the broker. [Q Cleanup Timer] INFO org.apache.activemq.broker.TransportConnection - The connection to 'vm://activemqbroker#0' is taking a long time to shutdown. Our activemq

JMSTimestamp on DLQ messages

Hi, How to get the My the timestamp of message created in DLQ in ActiveMQ 5.3? The JMSTimestamp header property seems to contain the original timestamp of message on it main Q not the time it ended up in DLQ. I am sure that in 5.2 JMSTimestamp value was always the timestamp of message created

Messages are left in memory with JDBC persistance for queues when no consumers

Hi, I have noticed that ActiveMQ is keeping the List of Message objects in memory after persisting them in the DB when there is no consumer on the queue. What I did is a simple test, I kept on sending persistent messages to a queue with no active consumers. The broker kept on using more memory

Re: Separate DLQ for each topic subscriber

Can someone please reply? -- View this message in context: http://www.nabble.com/Separate-DLQ-for-each-topic-subscriber-tp22252210p22293845.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: How does Producer flow control work with JDBC persitance?

Anyone? -- View this message in context: http://www.nabble.com/How-does-Producer-flow-control-work-with-JDBC-persitance--tp22007477p22293863.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

How does Producer flow control work with JDBC persitance?

I read below link about producer flow control but I am still confused about how it works when we have JDBC only persistance. http://activemq.apache.org/message-cursors.html I am noticing that ActiveMQ blocks even with JDBC only persistance but it doesn't make sense to me as to why it should

Re: Stuck messages - Dispatch issues

I tried 5.2 RC3 and it seem to have new bugs. It dispatching duplicates. One of my test run resulted below: Messages sent: 1000 (using 50 threads 20 times) Consumers: 2 trasacted Queue Attributes in JConsole: DequeCount: 1000 DipatchCount: 4849 EnqueueCount:1000 InFlightCount: 3849 QueueSize:

Stuck messages - Dispatch issues

We are seeing issues with ActiveMQ 5.1 and 5.2 RC2 with message dispatching from queues. It is easily reproducible even using the out of the box activemq configuration. Send messages to the a queue (QueueA) using multiple threads (10 or 20 thread in a loop of 10) using JMeter or your custom