'Client already connected ' exception in ActiveMQ v5.11.1

Hi, Setup: ActiveMQ v5.11.1 Clients connect to ActiveMQ server via load balancer Client is a durable stomp subscriber on a topic I have come across a weird case where I am getting a 'client already connected from some ip' exception but there is not client running and the durable subscriber is mar

DLQ.DLQ.*, DLQ.DLQ.DLQ.* entries. Duplicate DLQ-messages using Journaling.

Hello. I'm having a hard time figuring out why my broker is 'occasionally' creating extra DLQ-queues holding duplicate messages. Browsing the admin console, I'm seeing something like this: - DLQ.myEventQueue - DLQ.DLQ.myEventQueue They both hold a message with the same message ID, eg. ID:Clien

Re: Active MQ Shared File System Master Slave with Elastic File System

Thanks Tim. I'll get this up on JIRA soon. -- View this message in context: http://activemq.2283324.n4.nabble.com/Active-MQ-Shared-File-System-Master-Slave-with-Elastic-File-System-tp4715818p4715867.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.