[rabbitmq-discuss] rabbitmq-erlang-client rpc zombie process after broker restart
Matthias Radestock
matthias at rabbitmq.com
Mon Sep 9 04:45:20 BST 2013
Jan,
On 03/09/13 16:46, Jan Jacobs wrote:
> amqp_rpc_server.erl use the default options to create the queue used for
> the RPC.
>
> The queue attributes are as follows:
>
> -record('queue.declare', {ticket = 0, queue = <<"">>, passive = false,
> durable = false, exclusive = false, auto_delete = false, nowait = false,
> arguments = []}).
>
> This results in a non durable queue. Thus if the broker restarts, the
> queue will terminate and not be available on restart.
I've raised a feature request to make durability and other settings
configurable.
> The gen server process will remain alive and not terminate and rendering
> it unusable.
That's really a separate issue. I've filed a bug to address it. You can
work around it by, say, linking the server process to the connection
process.
Regards,
Matthias.
More information about the rabbitmq-discuss
mailing list