Hi,
I changed the implementation from receiveNoWait() to receive(1) but it did
not change anything in the behavior.
After the client crashes I can still see the delivered message in the Queue
(using browse) but no receive() call can get this message again, it seems to be
stuck in the queu
Hi,
here is a JUnit test (see below) I wrote to simulate the crash of a
worker and the expected redelivery behavior:
You have to replace _connectionProvider.getConnection(queueName); with
some code of you own to get you a Connection to the Queue.
The CrashingWorker does not commit or rollback the
Well,
if I understand you correctly then after the default timeout of 3ms is
reached the connection should disappear and the message should be redelivered
to another client. As said before, some messages were redelivered others simply
"disappeared".
Are the messages that are redelivered vis
Hi,
at first we did not set a value explicitly, assuming that then the default
value would be used. But nothing happened.
We also tried to set it in the java.naming.provider.url, but were not sure if
this is valid. It also had no effect.
Bye,
Daniel
-Ursprüngliche Nachricht-
Von: Joe
