[rabbitmq-discuss] Server error during queue.declare call

Jeroen Janssen jeroen.janssen at gmail.com
Wed Mar 30 15:33:49 BST 2011


Hello,

I've been trying to find info about this in the mailinglist, but I
couldn't find the exact scenario (since most of the seemingly related
issues deal with clusters).

Hopefully someone will recognize the problem and/or can help solve
this issue?

We are using the RabbitMQ 2.2.0 on a single server setup (no cluster)
with a client using the py-amqplib library.

The client sometimes hangs in the queue declare call. And the server
logging contains the following error report:

=ERROR REPORT==== 30-Mar-2011::12:06:44 ===
** Generic server <0.23453.72> terminating
** Last message in was {'$gen_cast',
                           {method,
                               {'queue.declare',0,
                                   <<"a6aa528f-5ab7-11e0-8739-
b8ac6f88dcc2">>,
                                   false,false,false,true,false,
                                   [{<<"x-expires">>,signedint,
300000}]},
                               none}}
** When Server state == {ch,running,
1,<0.23414.72>,<0.23449.72>,undefined,
                            #Fun<rabbit_channel_sup.0.58069862>,none,
                            {set,0,16,16,8,80,48,
                                 {[],[],[],[],[],[],[],[],[],[],[],[],
[],[],
                                  [],[]},
                                 {{[],[],[],[],[],[],[],[],[],[],[],[],
[],[],
                                   [],[]}}},
                            1,
                            {[],[]},
                            {[],[]},
                            <<"guest">>,<<"/">>,<<>>,
                            {dict,0,16,16,8,80,48,
                                  {[],[],[],[],[],[],[],[],[],[],[],[],
[],[],
                                   [],[]},
                                  {{[],[],[],[],[],[],[],[],[],[],[],
[],[],[],
                                    [],[]}}},
                            {dict,0,16,16,8,80,48,
                                  {[],[],[],[],[],[],[],[],[],[],[],[],
[],[],
                                   [],[]},
                                  {{[],[],[],[],[],[],[],[],[],[],[],
[],[],[],
                                    [],[]}}},
                            <0.23411.72>,
                            {state,none,undefined}}
** Reason for termination ==
** {{timeout,{gen_server2,call,[<0.23461.72>,{init,false}]}},
    [{gen_server2,call,2},
     {rabbit_amqqueue,declare,5},
     {rabbit_channel,handle_method,3},
     {rabbit_channel,handle_cast,2},
     {gen_server2,handle_msg,2},
     {proc_lib,init_p_do_apply,3}]}

Does anyone know if this is a (known) issue with rabbitmq 2.2.0 or py-
amqplib? Or is this a 'new' issue?

Best regards,

Jeroen Janssen


More information about the rabbitmq-discuss mailing list