The Apache ActiveMQusers team is pleased to announce the release of
Apache NMS.ActiveMQ v1.7.2. This release contains a few important fixes
including a memory leak fix, users are urged to upgrade from previous
releases.
The Wiki Page for this release can be found here:
http://activemq.apache.o
Thanks Tim for the detailed email. When I do failover I see below exception in
our app logs.
org.apache.activemq.transport.failover.FailoverTransport Transport
(tcp://hdp132.lab1.ariba.com:61616) failed, attempting to automatically
reconnect java.io.EOFException: null
at java.
Hi Tim,
I said indexing was the point of contention after seeing that Thread
"ActiveMQ NIO Worker 169" was still working on
org.apache.activemq.store.kahadb.MessageDatabase.updateIndex even after >
3.5 minutes.
These are full thread dumps. I guess the lock (read lock) is held by threads
"ActiveMQ
Hi Tim,
exactly... According to http://camel.apache.org/jms.html section Concurrent
Consumin, we can configure concurrentConsumers option in one of the
following ways:
On the JmsComponent,
On the endpoint URI or,
By invoking setConcurrentConsumers() directly on the JmsEndpoint.
However, I tried t
Sorry Everyone - I missed that when reading the configs.
Thanks for pointing that out Tim - the configuration does look right.
> On Apr 7, 2016, at 10:00 PM, Tim Bain wrote:
>
> Although I've only used the string-based syntax (e.g.
> from("jms:MyQueue?concurrentConsumers=10") ) to specify the n