1 Reply Latest reply on Dec 24, 2004 12:31 AM by mazz

    NumberFormatException

    mazz Master

      Well, I think I answered all of my previous questions... yes, you need to serialize classes and yes, setting the binding host name of 127.0.0.1 means you have to be careful about which addresses you use (I think I was mixing localhost and 127.0.0.1 or something.)

      Anyway, I now think I am getting further along, but hit another exception. Searched the forum but didn't find anything about NumberFormatException.

      Here's what I'm getting:

      Calling remote echo server with locator uri of: socket://192.168.0.5:8084
      java.lang.NumberFormatException: For input string: "<garbage characters>"
       at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
       at java.lang.Integer.parseInt(Integer.java:468)
       at java.lang.Integer.parseInt(Integer.java:518)
       at org.jboss.remoting.transport.socket.SocketUtil.len(SocketUtil.java:35)
       at org.jboss.remoting.transport.socket.SocketClientInvoker.transport(SocketClientInvoker.java:179)
       at org.jboss.remoting.RemoteClientInvoker.invoke(RemoteClientInvoker.java:100)
       at org.jboss.remoting.Client.invoke(Client.java:175)
       at org.jboss.network.watchdog.command.echo.client.EchoCommandClient.makeInvocation(EchoCommandClient.java:46)
       at org.jboss.network.watchdog.command.echo.client.EchoCommandClient.main(EchoCommandClient.java:81)
      


      I think I'm close though. Not sure what this exception is telling me. Where I wrote <garbage characters> up above is where I see some garbage getting printed, as if some characters came over the socket that wasn't expected - it was supposed to be a number I assume.