The thread on which that event occurs becomes unresponsive. The queue status call is happening on a clojure.core.async thread servicing <! actions, but stops responding after that exception despite more posts to the channel to which <! is listening.
On Fri, Jul 24, 2015 at 7:20 PM, Michael Klishin < michael.s.klis...@gmail.com> 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, but one client is experiencing apparent thread death > > on a queue status operation when the connection times out on heartbeat. > > What do you mean by “thread death”? There’s simply a timeout exception > in a thread pool where consumer functions are executed. > -- > @michaelklishin, github.com/michaelklishin > -- You received this message because you are subscribed to the Google Groups "clojure-rabbitmq" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure-rabbitmq+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
