[rabbitmq-discuss] Capturing chang in IP address at the listener
Alan Antonuk
alan.antonuk at gmail.com
Tue Feb 4 05:22:40 GMT 2014
Sorry I must've glossed over your message earlier...
On Mon, Feb 3, 2014 at 1:47 AM, Lothe Shashank <
Shashank.Lothe at techmahindra.com> wrote:
>
>
> 1. I created a listener and a queue is created at the broker. I changed my
> system IP address and restarted network manager. I could ping to the broker
> with this new IP address. However the queue created at the broker still
> shows the old IP address and any message published on this queue after IP
> change is not received by the client. The amqp_simple_wait_frame_noblock()
> API does not give any error event for IP address change; it was giving
> AMQP_STATUS_TIMEOUT. Is there a way capture this run time IP address change
> at the listener?
>
What do you mean by 'listener'? Do you mean you change the IP address of
the machine running the broker, or the machine running the client?
>
> 2. I created two listener threads having separate connection. I turned off
> my network router. One listener was able to get
> AMQP_STATUS_SSL_ERROR/AMQP_STATUS_SSL_CONNECTION_FAILED error while the
> other listener was still giving AMQP_STATUS_TIMEOUT. I was expecting
> AMQP_STATUS_SSL_ERROR/AMQP_STATUS_SSL_CONNECTION_FAILED error at both the
> listener. What could be the reason for this behaviour?
>
AMQP_STATUS_TIMEOUT only means the timeout that was specified to
amqp_simple_wait_frame_noblock() was reached before data was available on
the socket, or an error occurred. Most likely the operating system hasn't
detected that the socket has been closed.
-Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140203/3e35d52a/attachment.html>
More information about the rabbitmq-discuss
mailing list