High CPU load with network connector, failover transport

Hi, We’ve noticed a regression in ActiveMQ 5.10.1 vs. 5.10.0 with a configuration similar to the following: Broker 1: networkConnector with static:(failover:(tcp://broker2 )?randomize=false&maxReconnectAttempts=0) Broker 2: networkConnector with static:(failover:(tcp://broker1 )?randomize=fal

Re: queued messages more than dequeued

But there are more than one connected and it is not as I expect one subscriber one ack two subscriber two ack?? It is not linear isn't it? El 19/02/2015 22:54, "artnaseef" escribió: > The dequeue count for Topics is based on the numbers of subscribers, so it > will be higher than the enqueue coun

Re: queued messages more than dequeued

The dequeue count for Topics is based on the numbers of subscribers, so it will be higher than the enqueue count when more than one subscriber is active. Unlike Queues, statistics on Topics are generally less useful than those on the individual subscriptions. -- View this message in context: h

Re: "java.lang.OutOfMemoryError" in consumer application

Try taking a stack dump of the process once in a while and look at the list of threads. There may be a leak, such as a connection leak, that needs to be addressed. Using the stack dump, it should be easy to identify which threads are being created and sticking around for a long time. -- View t

queued messages more than dequeued

hello, in topics overview i am seeing that dequeued messages are much more that queued messages. how can it be possible? -- View this message in context: http://activemq.2283324.n4.nabble.com/queued-messages-more-than-dequeued-tp4691763.html Sent from the ActiveMQ - User mailing list archive a

kahadb lock in logs

This has been occuring since version 5.10 for us. It appeared that if we run activemq as a different user than who owns the activemq files then the kahadb will lock up and activemq will crash. So we've made sure we chown user:user -R ./activemq then run (without sudo) ./activemq/bin/linux-x86-64/a

Ab Initio JMS Publish : org.apache.activemq.transport.RequestTimedOutIOException

Hello, We are connecting to ActiveMQ broker from Ab-initio with below JNDI settings. java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory # use the following property to configure the default connector java.naming.provider.url=failover:(ssl://testbrokerurl:61610

Re: ActiveMQ broker is stopping after it is unable to destroy inactive durable subscriber.

Did you read Paul Gale's email from 9/20 to see if his root cause could be yours as well? If it's not, Anuj replied to that thread later to say he saw the same problem; maybe the two of you can work together to figure it out and tell the rest of us... On Feb 18, 2015 7:39 AM, "bansalp" wrote: >

Re: "java.lang.OutOfMemoryError" in consumer application

This is caused by hitting the native thread limit for the user that ActiveMQ runs as, causing the JVM to be "unable to create a new native thread" as stated in the stack trace you quoted. Increase that user's maxproc setting in the Linux OS (I assume you're running Linux, since I don't think this

Re: ActiveMQ broker is stopping after it is unable to destroy inactive durable subscriber.

ping. -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-broker-is-stopping-after-it-is-unable-to-destroy-inactive-durable-subscriber-tp4691703p4691755.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

"java.lang.OutOfMemoryError" in consumer application

Hi, We sometimes face : Exception in thread "ActiveMQ Transport: tcp://mqbroker/*.*.*.*:61616@35637" java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:714) at java.util.concurrent.ThreadPoolExecutor.addWo