[rabbitmq-discuss] [rabbitmq-c] minimal network bandwidth requirement to API execute
alan.antonuk at gmail.com
Fri Feb 28 05:42:03 GMT 2014
80% packet loss? Are you able to run any TCP-based protocols over that with
success? Thats an incredibly high packet loss situation. Things like HTTP
don't work well at 40% packet-loss, I can't imagine much of anything would
work at that level.
In rabbitmq-c once you create the socket it is owned by the
amqp_connection_state_t. You can close the socket by doing an
On Thu, Feb 27, 2014 at 5:52 AM, Rohit Patle
<Rohit.Patle at techmahindra.com>wrote:
> Hi Jerry,
> Thank you for your reply.
> The network I am testing is with very high latency (around 80% packet
> loss). In this condition we observed that API's like amqp_login,
> amqp_channel_open, and amqp_queue_create is hanging indefinitely.
> We have also observed that there is no amqp_socket_close API in rabbitmq-c
> 0.4.1. How can I close the socket which was opened previously using
> amqp_socket_open API? Whether amqp_destroy_connection closes the socket
> opened earlier?
> Please suggest.
> This email (including any attachments) is intended for the sole use of the
> intended recipient/s and may contain material that is CONFIDENTIAL AND
> PRIVATE COMPANY INFORMATION. Any review or reliance by others or copying or
> distribution or forwarding of any or all of the contents in this message is
> STRICTLY PROHIBITED. If you are not the intended recipient, please contact
> the sender by email and delete all copies; your cooperation in this regard
> is appreciated.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss