Re: Disptach Queue filled up and consumer not consuming

[drunkKnight <up...@gmail.com>]

Hello,
This issue is resolved. I checked the thread dump and found out that the
consumer threads were in WAITING state.

Just briefing my error here so that if anyone with similar case hit this,
then, they can do a broader-level of debugging at their own. We had a
SlackAppenderFactory registered with Logger, and so whenever the logging was
above DEBUG (logging levels: INFO/DEBUG/WARN/ERROR, we had the threshold set
to DEBUG), we were reporting it to SLACK. Since the user events were
increasing and we were on an unpaid version, there was a throttling
exception thrown by SLACK that we were not anticipating (This code was
written around 2 years back and we never hit it).
Apart from IOException, every other error/exception would again be routed to
slack and thus the LOGGER was keeping a lock and no consumer could access it
(since we have LOGGER statement in almost every method). This resulted in
consumer-threads in WAITING state.

I wanted to report this earlier but got too busy so posting the abstract.



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html