users@activemq.apache.org
Subject: RE: AMQ fails to process messages after a faulty restart
Hi, I upgraded the AMQ to 5.5.0 since I saw a bug on this, however this still
reproduces in another way.
Now, I don't get the error in the AMQ as I wrote of 'Async error' but for some
reason some ti
nherits
from a Serializable class, might that be a problem?)
Thanks in advance, Michal
-Original Message-
From: Michal Singer
Sent: ג 29 מרץ 2011 16:16
To: users@activemq.apache.org
Subject: RE: AMQ fails to process messages after a faulty restart
But actually, after one message li
...@gmail.com]
Sent: ג 29 מרץ 2011 15:12
To: users@activemq.apache.org
Subject: Re: AMQ fails to process messages after a faulty restart
that exception is expected in some circumstances. The broker comes
alive again, the client using the failover transport resends an ack,
as it still has state.
The
that exception is expected in some circumstances. The broker comes
alive again, the client using the failover transport resends an ack,
as it still has state.
The broker has not yet dispatched any messages so it cannot ack the message.
There have been improvements in this area in 5.3, especially w
Hi, i am using AMQ 5.2.0 on a multi process application to communicate between
processes.
I am configuring AMQ using Spring version 2.5.6
I am NOT using persistent AMQ.
Sometimes after a faulty restart such as: kill java, electric power down -
after raise, there are errors:
ActiveMQ Transport: