QueueDeclare timeout exception

916 views
Skip to first unread message

Martin Pekurny

unread,
Oct 11, 2017, 1:20:59 PM10/11/17
to rabbitmq-users
I am getting a timeout when calling the QueueDeclare method. The stack trace is below. The details are that I installed 3.6.12 using the .NET Client 5.0.1 and get the error below. If I install the 3.6.10 version of the server I do not get the error. The code I am using is copy/paste from the C# tutorial at https://www.rabbitmq.com/tutorials/tutorial-one-dotnet.html. The installs are default, no plugins, no config changes. It doesn't seem to matter what version of the client (tried several, same results). However, when I use 3.6.11 or 3.6.12 it throws the exception every time I call QueueDeclare. Is there a change to the tutorial code to make it work with the new versions of the server?

   at RabbitMQ.Util.BlockingCell.GetValue(TimeSpan timeout)
   at RabbitMQ.Client.Impl.SimpleBlockingRpcContinuation.GetReply(TimeSpan timeout)
   at RabbitMQ.Client.Impl.ModelBase.QueueDeclare(String queue, Boolean passive, Boolean durable, Boolean exclusive, Boolean autoDelete, IDictionary`2 arguments)
   at RabbitMQ.Client.Impl.ModelBase.QueueDeclare(String queue, Boolean durable, Boolean exclusive, Boolean autoDelete, IDictionary`2 arguments)
   at Receive.Program.Main(String[] args) in D:\src\RabbitMQPOC\Receive\Program.cs:line 16

Luke Bakken

unread,
Oct 11, 2017, 5:47:57 PM10/11/17
to rabbitmq-users
Hi Martin,

I followed the tutorial one instructions and can't reproduce your issue. Here is my environment -

* Arch Linux, running .NET Core 2.0 (compile / run the tutorial code)
* RabbitMQ 3.6.12 (running from the stable branch of RabbitMQ)

It looks like you're using Windows to run the tutorial code. Are you also running RabbitMQ on Windows? If so, are you using the installer or binary release? Which version of Erlang? (that shouldn't really matter but you never know...)

Thanks -
Luke 

Martin Pekurny

unread,
Oct 11, 2017, 8:57:12 PM10/11/17
to rabbitmq-users
Yes. I am running RabbitMQ on the same machine connecting with localhost. I installed it with the installer and have Erlang 19.3 installed. I also tried it with Erlang 20.1 on 3.6.12, but it made no difference in the behavior. Also, I used a .NET Framework console application instead of Core. I used a few different versions of the Client, 5.0.1, 4.0.1, and 3.6.12.

Luke Bakken

unread,
Oct 11, 2017, 9:04:33 PM10/11/17
to rabbitmq-users
Thanks for the additional information. I will check this out on Windows tomorrow.

Luke

Luke Bakken

unread,
Oct 13, 2017, 9:16:05 PM10/13/17
to rabbitmq-users
Hi Martin,

I just tried to reproduce this scenario using RabbitMQ 3.6.12 (installed via the .exe installer) and Erlang 20.1 running on my Windows 10 workstation, but everything works fine.


At first I thought you might be having an issue with the windows firewall but with 3.6.10 working I'm not so sure.

Could you give it a try running the code from the repository I link to above?

Thanks -
Luke

On Wednesday, October 11, 2017 at 5:57:12 PM UTC-7, Martin Pekurny wrote:

Martin Pekurny

unread,
Oct 15, 2017, 5:31:23 PM10/15/17
to rabbitmq-users
Ok, I tried this on another computer and everything worked just fine. So it's something specific to my machine at work. I will attempt to uninstall everything in the morning again and start over. I will reply again with any more details tomorrow.

Luke Bakken

unread,
Oct 15, 2017, 5:36:16 PM10/15/17
to rabbitmq-users
Hi Martin,

If you can, check to see if anti-virus software is installed and flagging the 3.6.12 .exe installer as malicious. Just an idea.

Thanks for the update -
Luke

Martin Pekurny

unread,
Oct 16, 2017, 9:44:10 AM10/16/17
to rabbitmq-users
So this morning I uninstalled RabbitMQ and Erlang. I then went through and deleted everything left behind by both installers. For RabbitMQ I didn't find much, a couple directories weren't cleaned up and the stuff in my profile. But for Erlang, it left some executables and processes running. After rebooting a couple times, I was able to remove them. After I was fairly certain I had gotten everything removed, I reinstalled Erlang 20.1 and RabbitMQ 3.6.12 and everything started working for me. I am guessing something left behind, most likely the executables by Erlang, were the cause of my issues.

So it looks like I am up and running again. Thanks for looking into this for me.

pantonis

unread,
Oct 27, 2017, 11:04:38 AM10/27/17
to rabbitmq-users
I have the exactly the same problem. I have installations on several  servers but only on my machine I experience this problem. After I restart broker and sometime delete the queue the problem is solved.
May I ask if it is possible to list all the steps you followed?

Thanks

Kuo Patrick

unread,
Dec 22, 2017, 4:42:35 AM12/22/17
to rabbitmq-users
I am having this issue as well, but only happen on my Laptop,not on my PC. After I restart broker it goes fine.

this is the log: 


=SUPERVISOR REPORT==== 22-Dec-2017::15:35:15 ===
     Supervisor: {<0.1610.0>,rabbit_channel_sup}
     Context:    shutdown_error
     Reason:     killed
     Offender:   [{pid,<0.1613.0>},
                  {name,channel},
                  {mfargs,
                      {rabbit_channel,start_link,
                          [1,<0.1601.0>,<0.1611.0>,<0.1601.0>,
                           <<"127.0.0.1:50089 -> 127.0.0.1:5672">>,
                           rabbit_framing_amqp_0_9_1,
                           {user,<<"guest">>,
                               [administrator],
                               [{rabbit_auth_backend_internal,none}]},
                           <<"/">>,
                           [{<<"publisher_confirms">>,bool,true},
                            {<<"exchange_exchange_bindings">>,bool,true},
                            {<<"basic.nack">>,bool,true},
                            {<<"consumer_cancel_notify">>,bool,true},
                            {<<"connection.blocked">>,bool,true},
                            {<<"authentication_failure_close">>,bool,true}],
                           <0.1602.0>,<0.1612.0>]}},
                  {restart_type,intrinsic},
                  {shutdown,70000},
                  {child_type,worker}]




pantonis於 2017年10月27日星期五 UTC+8下午11時04分38秒寫道:

Michael Klishin

unread,
Dec 24, 2017, 12:36:59 AM12/24/17
to rabbitm...@googlegroups.com
That exception simply means a channel failed to shut down in time and was forcefully terminated.

Nothing else. Not a whole lot of conclusion can be derived from it.

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+unsubscribe@googlegroups.com.
To post to this group, send email to rabbitmq-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
MK

Staff Software Engineer, Pivotal/RabbitMQ
Reply all
Reply to author
Forward
0 new messages