[rabbitmq-discuss] AMQP Connection gets forcibly closed : .Net client

[Eric@SPIN]

Hi Matthias,

This is the exact error where are getting...

The AMQP operation was interrupted: AMQP close-reason, initiated by Peer,
code=320, text="CONNECTION_FORCED - broker forced connection closure with
reason 'shutdown'", classId=0, methodId=0, cause=

I've checked your reply. I've been assured that nobody shut-down the broker.
This has happened twice today. In both cases re-starting our application we
were able to progress. Could there be any other reason? By the way we are
now on version 2.1.1.0

Regards,

Eric


Matthias Radestock-2 wrote:
> 
> Rajesh,
> 
> 
> Reddy, Rajesh (GPT EMEA) wrote:
>> We are using the .NET client and the heartbeat is set to 60 sec for the
>> connection. We are getting the following exception some times and the
>> client losses the connection.
>> 
>> AMQP Connection closed. Initiator:Peer Reason:CONNECTION_FORCED - broker
>> forced connection closure with reason 'shutdown'
> 
> That message originates at the broker when it performs a controlled 
> shutdown. So it should not come as a surprise, unless somebody is 
> shutting down your rabbit broker without telling you.
> 
> 
> Regards,
> 
> Matthias.
> 
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> 
> 

-- 
View this message in context: http://old.nabble.com/MulticastMain-Java-client-causes-Erlang-error-eheap_alloc%3A-Cannot-allocate-467078560-bytes-of-memory-%28of-type-%22heap%22%29-%28with-RabbitMQ-1.7.1%29-tp27311241p30011591.html
Sent from the RabbitMQ mailing list archive at Nabble.com.