9 Replies Latest reply on Feb 13, 2007 2:34 PM by Alex Colomb

    SocketClientInvoker switching addresses?!?!

    Alex Colomb Newbie

      We are having a very strange issue with both 1.0.1Sp2 and 1.0.1SP4 where one of our messaging clients never gets any messages. After turning some TRACE level output (thanks for the page on how to do that!) we noticed this little line;

      2007-02-12 15:16:24,251 79023 DEBUG [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] @WorkerThread#4[10.100.1.22:57814] SocketClientInvoker[141cd01, socket://127.0.0.1:3153] setting client socket wrapper class name to org.jboss.jms.client.remoting.ClientSocketWrapper
      


      It looks like the remoting layer is somehow translating the 10.100.1.22 ip to 127.0.0.1. When other clients register (that work), the two ips match:

      2007-02-12 15:19:12,328 247100 DEBUG [org.jboss.remoting.transport.socket.MicroSocketClientInvoker] @WorkerThread#5[10.100.1.40:34595] SocketClientInvoker[344422, socket://10.100.1.40:2725] setting client socket wrapper class name to org.jboss.jms.client.remoting.ClientSocketWrapper
      


      Thank you.