<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 11, 2017 at 5:48 PM, Gustavo Fernandes <span dir="ltr"><<a href="mailto:gustavo@infinispan.org" target="_blank">gustavo@infinispan.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class="">On Fri, Aug 11, 2017 at 3:30 PM, Sanne Grinovero <span dir="ltr"><<a href="mailto:sanne@infinispan.org" target="_blank">sanne@infinispan.org</a>></span> wrote:<br></span><div class="gmail_extra"><div class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 11 August 2017 at 14:14, Galder Zamarreño <<a href="mailto:galder@redhat.com" target="_blank">galder@redhat.com</a>> wrote:<br>
> Hi,<br>
><br>
> Re: <a href="https://issues.jboss.org/browse/ISPN-8186" rel="noreferrer" target="_blank">https://issues.jboss.org/brows<wbr>e/ISPN-8186</a><br>
><br>
> I've been looking at TRACE logs and what seems to happen is that is that sometimes, when the client needs to create a new Socket, it sends using the same localport as the Hot Rod server port. As a result, when the client sends something to the server, it also receives it, hence it ends finding a request instead of a response. Analysis of the logs linked in the JIRA can be found in [1].<br>
><br>
> What I'm not sure about is how to fix this... There are ways to potentially pass a specific localport to a Socket [2] but this could be a bit messy: It'd require us to generate a random local port and see if that works, making sure that's not the server port...<br>
><br>
> However, I think the real problem we're having here is the fact that both the server and client are bound to same IP address, 127.0.0.1. A simpler solution could be a way to get the server to be in a different IP address to the client, but what would that be that IP address and how to make sure it always works? Bind the server to eth0?<br>
><br>
> Any other ideas?<br>
<br>
</span>You could create multiple aliases for the same loopback device, and<br>
assign a different IP address to each of them.<br></blockquote><div><br></div></span><div>No need for aliases, we could use directly use any IP from the range <a href="http://127.0.0.0/8" target="_blank">127.0.0.0/8</a><br></div><div>Just a reminder, the testsuite should be able to run on Linux/Win/MacOS so I'd stay <br></div><div>away for OS specific extra steps<br></div></div></div></div></blockquote><div class="m_-2809505067532954307h5"><br><br></div><div class="m_-2809505067532954307h5">I tested on a recent Linux and Win, it works, but MacOS requires an alias to be created...<br><br><br></div><div class="m_-2809505067532954307h5"><br></div></div></div></div>