artnaseef wrote > Hmm, check the producer connections to the broker after the VPN restart > using netstat. > > When the consumers appear to hang, do you see evidence on the broker that > the producer messages are actually being received in the broker? For > example, the QueueSize for the queue -- is it increasing over time? > > What does jstack show the consumer threads doing? > > Note that with certain configurations on the producers, the ActiveMQ > client library may use asynchronous sends to push the messages across the > transport to the broker, so the producers may appear to be actively > sending even though the messages aren't making it to the broker.
The producer connection is just fine. When it sends a message it receives a response back saying it received the message. We have trace enabled on the transport. The consumers are blocked waiting for messages. They are blocked at the same spot as if their was no messages on the queue. When Activemq is in this state I can see the queue size growing using JConsole. I can see the Queue Cursor size growing by the log statements as well as setting breakpoints in the activemq code, but I believe there is a flag set that says there is no messages in the cursor and it does not send the message on to the consumers. I have been running for a few days now with the producer sending non persistent messages and it has been running fine. I believe there is a bug in activemq on how it handles a persistent message being sent to a broker that has persistents disabled and it receives a duplicate message as soon as a failover transport comes back. -- View this message in context: http://activemq.2283324.n4.nabble.com/Consumer-hanging-after-a-producer-fails-for-being-inactive-tp4689775p4690049.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
