Re: AMQ 5.13.2 : Kaha DB logs cleanup issue

Thanks Tim, I did not know that the stats are reset when the broker is restarted. I'll check how to use JConsole to view the current status of consumers. Yes, all topics have durable subscribers. I used the logic mentioned in the example given at

new Active MQ jars with spring classes embedded inside

Hi All, We have a legacy application and are in the process of migrating to the latest active mq jars due to some security vulnerabilities in the versions below 5.13.x. But what we are finding is that the new jars have spring modules embedded inside the jar ( as folders with classes and not

Re: AMQ 5.13.2 : Kaha DB logs cleanup issue

As far as I know, the stats cover only the time since the broker was last restarted, so seeing zeros is no guarantee that there are no pending messages in the persistence store. I would use a JMX viewer such as JConsole to look at what the broker thinks is the current status of the consumer(s) on

Re: Broker network disconnecting every minute

The same behavior occurs when using tcp transport instead of ssl. The network is stable (I can even reproduce this when running two brokers on the same system). I am currently using ActiveMQ 5.13.1, but had the same problem with previous versions. -- View this message in context:

Re: How can i get Broker Service instance of the remote broker ?

yes , i have to have the session count because of one reason we had a very bad problem with one of the producer while performing a heavy load test where client never closed their sessions in this test and with in a short amount of time broker going down and we had the issue when we do restarts as

ActiveMQ memory usage, persistent messaging, cursor usage and PFC

Hi, I'm relatively new to ActiveMQ and currently I try to understand the various information about persintence, Memory limit, Cursor memory limit, Cursur percent usage and Producer Flow Control. (I' m sure I read almost all available information, especially

AMQ 5.13.2 : Kaha DB logs cleanup issue

We use AMQ to exchange MQTT messages. I observed that the log files in Kaha DB don't get deleted even after many days. I used the steps mentioned in http://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html

Re: [Artemis, Qpid JMS] Connection limit

On 16 May 2016 at 13:37, Vavricka wrote: > It is probably linked to allowed Anonymous access. It looks like that user is > ignored and Anonymous acces is used. And there is no limit for anonymous > user. > > DEBUG org.apache.qpid.jms.sasl.SaslMechanismFinder - Skipping