run(TcpTransport.java:186)
>at java.lang.Thread.run(Thread.java:619)
>
>
> Shouldn't this exception end up somewhere in the ActiveMQ server code ?
>
>
> Bye,
> Daniel
>
> -Ursprüngliche Nachricht-
> Von: Gary Tully [mailto:gary.tu...@gmail.com]
&g
I just had a cursory look at the code and I think the receiveNoWait() call
may be part of the problem.
receiveNoWait does not work well with activemq just after a consumer has
been created. It can take some time for the consumer to register and
dispatch to occur and it ocurrs async to the receiveN
Your first assumption about automatic redelivery is correct. Any unacked
message will be redelivered. They may not get redelivered to the same
consumer though, any consumer will do from the brokers perspective. The
first precondition though is the recognition of the death of the consumers
connectio
The InactivityMonitor should have detected the failed connection. What value
did you assign to maxInactivityDuration? By default it is set to 3ms.
Joe
ActiveMQ Ref Guide - http://bit.ly/AMQRefGuide
daniel.stucky-2 wrote:
>
> Hi ActiveMQ Team,
>
>
>
> in the eclipse open source projec
