You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have come across the scenario that the library throws a SocketException in SocketFrameHandler constructor when it tries to connect through IPV6. It the successfully connects using IPv4.
This is not a problem most of the times but for low latency systems when memory is important is kind of expensive to throw exception every time a connection is being established, especially when there are a number of connections.
Is it possible to somehow pass the socket address type as parameter to avoid this?
Thanks
The text was updated successfully, but these errors were encountered:
Can you please provide an example code snippet, library and OS version details?
RabbitMQ connections are supposed to be long lived so I am not buying into the argument that throwing and catching an exception is expensive. If it is then you should be using a memory managed runtime to begin with.
That said, forcing IPv6 or IPv4 is a fairly reasonable request.
michaelklishin
changed the title
Socket.OSSupportsIPv6
Forcing connection over IPv6 or IPv4
Jul 28, 2016
I am currently running on Windows 10 and windows server 2012 r2.
"RabbitMQ connections are supposed to be long lived" I know that. I was speaking about scenarios that connectivitity is lost due to network problems. Unfortunately in a low latency system I don't have the flexibility to throw exceptions.
Hi,
I have come across the scenario that the library throws a SocketException in SocketFrameHandler constructor when it tries to connect through IPV6. It the successfully connects using IPv4.
This is not a problem most of the times but for low latency systems when memory is important is kind of expensive to throw exception every time a connection is being established, especially when there are a number of connections.
Is it possible to somehow pass the socket address type as parameter to avoid this?
Thanks
The text was updated successfully, but these errors were encountered: