Simon MacMullen <simon@...> writes:

On 19/05/13 22:56, Matthias Radestock wrote:
To help us track down the cause of the bug, it would be good to know
whether your applications use AMQP transactions.
To expand this: we have replicated this issue when transactions are in
use (and will have a fix in the next release). But if you can make this
happen without using transactions, we'd really like to hear from you.

Cheers, Simon

Hi Simon & Matthias,

We have only noticed the issue when transactions are enabled and we use
transactions on all our queues. I only really need to restart the node when
I find the strange:

   "INFO: task beam.smp:18971 blocked for more than 120 seconds."

logs in my /var/syslog (which seems to be another unrelated issue with
flushing data in memory to disk on EC2).

Thanks a lot for replying so quickly and letting me know about the bug and
future bug fix. We really appreciate it!

Let me know if there is any other information you guys would like to help
with the bug fix.


Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 7 of 8 | next ›
Discussion Overview
grouprabbitmq-discuss @
postedMay 18, '13 at 3:20a
activeMay 20, '13 at 2:12p



site design / logo © 2017 Grokbase