[rabbitmq-discuss] The rabbitmq-server stop command hangs
Tim Watson
tim at rabbitmq.com
Wed Nov 28 11:55:40 GMT 2012
On 28 Nov 2012, at 11:42, Matthias Radestock wrote:
> On 28/11/12 11:29, Tim Watson wrote:
>> Can you please confirm a couple of things for us: what plugins are
>> enabled in your setup?
>
> See Liz' earlier post:
> <quote>
> # rabbitmqctl eval 'app_utils:app_dependency_order([os_mon,
> mnesia,rabbit] ++ rabbit_plugins:active(),true).'
> [mnesia,mochiweb,amqp_client,webmachine,rabbitmq_mochiweb,os_mon,rabbit,
> rabbitmq_management_agent,rabbitmq_shovel,rabbitmq_management]
> </quote>
>
> I asked for this since it wasn't obvious to me
> that the shutdown was hanging in the rabbit application.
>
> If it isn't rabbit, then a prime candidate from the above list would be shovel.
>
Sounds quite likely.
> rabbit_net:recv is the normal place for the reader to sit when nothing
> is happening. It has a catch-all 'Other' clause.
>
Right, so tcp events will come back that way too, got it.
More information about the rabbitmq-discuss
mailing list