Hello,
we have upgraded from 5.3.x series to a snapshot version because we
got several KahaDB errors. It was fine for a long time but then we
suddenly had an KahaDB error again. Any idea where is this coming
from? I assume its again something on creating index or such.
Thanks for any tips,
Christ
nothing. Without the slave consumers are leaving and the webapp
shows zero of them.
Attached is a thread dump. Any ideas why this happens? I am not having
a clue anymore :-(
Christian
On Wed, May 19, 2010 at 3:34 PM, Christian Grobmeier
wrote:
> We are not aware of any consumers having trouble.
.processDispatch(TransportConnection.java:802)
> at
> org.apache.activemq.broker.TransportConnection.iterate(TransportConnection.java:838)
> at
> org.apache.activemq.thread.DedicatedTaskRunner.runTask(DedicatedTaskRunner.java:98)
> at
> org.apache.activemq.thread.DedicatedTaskR
I am a collegue of Andreas. It happened again on tuesday but again we don't
know the reasons. Attached are two thread dumps. I cannot see anything in
it, but maybe you are seeing more.
http://old.nabble.com/file/p28607920/dumps.zip dumps.zip
We had also problems with KahaDB before which forced
