DefaultExceptionHandler in Java closes the channel after an unhandled
exception. There is more forgiving version available in 3.5.4. Doing your own
handling is a good idea anyway.
MK
> On 25/7/2015, at 19:43, Dave Tenny wrote:
>
> The thread on which that event occurs becomes unresponsive. T
Of course it's possible it has nothing to do with Langohr/RabbitMQ, but
most of our code works just fine with the Langohr autorecovery stuff, i.e.
we don't have to do much, if anything. It's only this thread doing the
queue status operation that is going AWOL.
On Sat, Jul 25, 2015 at 12:43 PM, Da
The thread on which that event occurs becomes unresponsive. The queue
status call is happening on a clojure.core.async thread servicing wrote:
> On 24 Jul 2015 at 21:21:39, Dave Tenny (dave.te...@gmail.com) wrote:
> > I have a number of rabbitmq clients, most of which fail over well
> > enough,
On 24 Jul 2015 at 21:21:39, Dave Tenny (dave.te...@gmail.com) wrote:
> I have a number of rabbitmq clients, most of which fail over well
> enough, but one client is experiencing apparent thread death
> on a queue status operation when the connection times out on heartbeat.
What do you mean
I have a number of rabbitmq clients, most of which fail over well enough,
but one client is experiencing apparent thread death on a queue status
operation when the connection times out on heartbeat.
I wondered if anybody had any clues here. Note the
langohr.queue$status.invoke()
Exception in t
