activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From berges <ber...@mesan.no>
Subject DLQ.DLQ.*, DLQ.DLQ.DLQ.* entries. Duplicate DLQ-messages using Journaling.
Date Fri, 26 Aug 2016 09:04:19 GMT
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:ClientABC-61753-1471513949441-1:4:1:3:1	

The one from DLQ.myEventQueue is a standard entry caused by a client
transaction rollback.
The (unwanted) one from DLQ.DLQ.myEventQueue has a
- dlqDeliveryFailureCause: java.lang.Throwable: duplicate paged in from
store for queue://DLQ.eAdminESBEventQueue

At some point I might even get a third queue named
- DLQ.DLQ.DLQ.myEventQueue holding another message with the samme MessageID
and the same dlqDeliveryFailureCause 

The ActiveMQ broker is set up in a semi-active test environment with
multiple clients. 

Note: We are in the process of upgrading from 5.7 to 5.14. I may missed some
vital information about configuration changes...I'm guessing there is some
issue with the use of Journaling and synchronization between Kahadb and the
MSSQL-database. Please have a look at the attaced configuration file 
activemq-anonymous.xml
<http://activemq.2283324.n4.nabble.com/file/n4715868/activemq-anonymous.xml>   

Going through the Issue Tracker I found relevant (resolved) bugs in
https://issues.apache.org/jira/browse/AMQ-4485 and
https://issues.apache.org/jira/browse/AMQ-5266.

- ActiveMQ version: 5.14.0
- JDK: 1.8.0_93
- OS: Windows Server 2012 R2, 64Bit, 4GB RAM, Installed with 64 Windows
Service.
- Standard Jetty-configuration
- Log output: I've enabled DEBUG, but I can't find a way to provoke the
error. It can take days before another DLQ.DLQ-entry occurs. In my
log4j-configuration I have to limit the size of my log-files, due to limited
disk space on  the server. And with DEBUG enabled they fill up relatively
quickly. 

Any input or suggestions would be greatly appreciated. 



--
View this message in context: http://activemq.2283324.n4.nabble.com/DLQ-DLQ-DLQ-DLQ-DLQ-entries-Duplicate-DLQ-messages-using-Journaling-tp4715868.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message