Re: KahaDb journal file are not getting recycled and "Total Message Count" is negative

Thanks Tim, Subscribers only subscribe to queues. I restarted the server, but, that didn't fix the problem either, haven't tried destroying all destinations yet. The problem occurred in production, we have to drain all the queues and start with a new kahadb to solve the problem. I took backup of

Re: KahaDb journal file are not getting recycled and "Total Message Count" is negative

Yes, all the queues are empty, enqueue and dequeue counts were off for a couple of queues, probably, because I purged them. I am running 5.11.1, all the queues are consuming messages from virtual topics and advisory messages are disabled. -- View this message in context: http://activemq.22833

Re: KahaDb journal file are not getting recycled and "Total Message Count" is negative

Thanks Tim, there are no durable subscribers, this server does not have any networked brokers either. Went though JMX information, but, nothings seems out of ordinary. Except that the total dequeue count (118) is less than total enqueue count (242). I know about heckForCorruptJournalFiles, but,

How to remove "ActiveMQ" prefix from DLQ names

I am using "individualDeadLetterStrategy" to create individual DLQs for queues and topics but the created DLQ has an ActiveMQ prefix, is this expected? and is there are way to remove it? I am using the following destinationPolicy

KahaDb journal file are not getting recycled and "Total Message Count" is negative

I removed all the messages from all the queues but the kahan db files are not getting recycled. Hawtio is showing that the total message count is -59. I am using the following mKahaDB configs.

Dlq attribute = false for DLQs created with individualDeadLetterStrategy

I am creating individual DLQ per queue and topic, with the following config, but the Dlq attribute of the created queues is false. Is this expected, I don't get option to replay the messages in the console for these DLQs either.

ActiveMQ .Net: Difference between NMSXGroupID and JMSXGroupID

Hi everyone, I am trying to understand how the .Net Apache.NMS.ActiveMQ client handles standard JMS properties. Message group is properly set when I use "NMSXGroupID" property but not with "JMSXGroupID". Is this expected? Shouldn't .Net client support the standard JMS header strings? Thanks. Fa

Re: Artemis: JMSXGroupID / Message groups: Large number of groups

Great question, would love to hear the best way to solve this problem. I ran into the same problem recently while using "classic" ActiveMQ, in my particular use case it was hard to predict the number of concurrent active groups, therefore, I ended up switching to simpleMessageGroupMapFactory and