[rabbitmq-discuss] Consumer connection closes abruptly after one message

[p2w]

Right, the doc indicates that for Thin you do an
EventMachine.next_tick {.......}, which was my first pass approach...

separately, when i try to use the approach in that gist you pointed me
at it is not reading the amqp.yml file properly. is there a particular
format it wants? I am using uri's in that file....can you let me know
if it wants something specific? here is the current format of that
file i looked at the doc and it should be working...but it keeps
trying to connect to localhost...:

development:
  uri: amqp://###:####@mq.#########.com/test
test:
  uri: amqp://###:####@mq.#########.com/test
sandbox:
  uri: amqp://###:####@mq.#########.com/sandbox
staging:
  uri: amqp://###:####@mq.#########.com/staging
production:
  uri: amqp://###:####@mq.#########.com/barzmedia

On Nov 16, 12:18 pm, Michael Klishin <michael.s.klis... at gmail.com>
wrote:
> Le 16/nov/2011 à 21:11, p2w a écrit :
>
> > This makes me pretty sure this is
> > an issue with Thin/EM blocking AMQP at thread level. I can replicate
> > this consistently.
>
> With Thin you do not typically start EventMachine in a separate thread. This is the case with Unicorn and Passenger but almost never with Thin.
>
> This can be an EventMachine issue. We depend on EventMachine for TCP connection failure notifications. Maybe try EventMachine 1.0 pre-releases? amqp gem will work with that and we run CI against that version against 7 Rubies or so.
>
> MK
>
> http://github.com/michaelklishinhttp://twitter.com/michaelklishin
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-disc... at lists.rabbitmq.comhttps://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss