Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6677864

Malformed reply from SOCKS server when using webstart version 1.6.0_05

XMLWordPrintable

    • x86
    • windows_xp

      FULL PRODUCT VERSION :
      JRE 1.5.0_14 (client)

      ADDITIONAL OS VERSION INFORMATION :
      Windows XP 2002 sp2

      EXTRA RELEVANT SYSTEM CONFIGURATION :
      OAS 10.1.2 hosting EJB components

      A DESCRIPTION OF THE PROBLEM :
      When executing an application using webstart version 1.6.0_05 where the client is using JRE 1.5.0_14, if the application tries to perform a remote EJB lookup, a NamingException is returned, caused by a SocketException.

      This problem is occurring where the user is on a different network domain to the server instance.

      This error is only returned using this combination of webstart version and JRE version - downgrading webstart to 1.6.0_03 or downgrading to JRE 1.5.0_05 stops the error occurring and the lookup continues without a problem.

      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      Launch a webstart application which uses a remote EJB lookup with webstart version 1.6.0_05 and JRE 1.5.0_14

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      The RMI InitialContext lookup returns the expected value
      ACTUAL -
      Stack trace produced in console window (see error message input on this bug report)

      ERROR MESSAGES/STACK TRACES THAT OCCUR :
      javax.naming.NamingException: Lookup error: java.net.SocketException: Malformed reply from SOCKS server; nested exception is:
      java.net.SocketException: Malformed reply from SOCKS server [Root exception is java.net.SocketException: Malformed reply from SOCKS server]
      at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:168)
      at javax.naming.InitialContext.lookup(Unknown Source)
      at com.evotecoai.esma.EsmaHelper.initBeans(EsmaHelper.java:1115)
      at com.evotecoai.esma.EsmaHelper.<init>(EsmaHelper.java:148)
      at com.evotecoai.esma.EsmaHelper.createInstance(EsmaHelper.java:950)
      at com.evotec.aplus.loader.APlusLoader.main(APlusLoader.java:424)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at com.sun.javaws.Launcher.executeApplication(Unknown Source)
      at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
      at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
      at com.sun.javaws.Launcher.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)
      Caused by: java.net.SocketException: Malformed reply from SOCKS server
      at java.net.SocksSocketImpl.readSocksReply(Unknown Source)
      at java.net.SocksSocketImpl.connect(Unknown Source)
      at java.net.Socket.connect(Unknown Source)
      at java.net.Socket.connect(Unknown Source)
      at java.net.Socket.<init>(Unknown Source)
      at java.net.Socket.<init>(Unknown Source)
      at com.evermind.server.rmi.RMIConnection.connect(RMIConnection.java:2346)
      at com.evermind.server.rmi.RMIConnection.lookup(RMIConnection.java:1800)
      at com.evermind.server.rmi.RMIServer.lookup(RMIServer.java:676)
      at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:149)
      ... 14 more
      javax.naming.NamingException: Lookup error: java.net.SocketException: Malformed reply from SOCKS server; nested exception is:
      java.net.SocketException: Malformed reply from SOCKS server [Root exception is java.net.SocketException: Malformed reply from SOCKS server]
      at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:168)
      at javax.naming.InitialContext.lookup(Unknown Source)
      at com.evotecoai.esma.EsmaHelper.initBeans(EsmaHelper.java:1115)
      at com.evotecoai.esma.EsmaHelper.<init>(EsmaHelper.java:148)
      at com.evotecoai.esma.EsmaHelper.createInstance(EsmaHelper.java:950)
      at com.evotec.aplus.loader.APlusLoader.main(APlusLoader.java:424)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
      at java.lang.reflect.Method.invoke(Unknown Source)
      at com.sun.javaws.Launcher.executeApplication(Unknown Source)
      at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
      at com.sun.javaws.Launcher.doLaunchApp(Unknown Source)
      at com.sun.javaws.Launcher.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)
      Caused by: java.net.SocketException: Malformed reply from SOCKS server
      at java.net.SocksSocketImpl.readSocksReply(Unknown Source)
      at java.net.SocksSocketImpl.connect(Unknown Source)
      at java.net.Socket.connect(Unknown Source)
      at java.net.Socket.connect(Unknown Source)
      at java.net.Socket.<init>(Unknown Source)
      at java.net.Socket.<init>(Unknown Source)
      at com.evermind.server.rmi.RMIConnection.connect(RMIConnection.java:2346)
      at com.evermind.server.rmi.RMIConnection.lookup(RMIConnection.java:1800)
      at com.evermind.server.rmi.RMIServer.lookup(RMIServer.java:676)
      at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:149)
      ... 14 more


      REPRODUCIBILITY :
      This bug can be reproduced always.

      CUSTOMER SUBMITTED WORKAROUND :
      Changing webstart version to 1.6.0_03 or changing JRE to version 1.5.0_05 seems to work.

      Release Regression From : 6u3
      The above release value was the last known release where this
      bug was not reproducible. Since then there has been a regression.

            dgu Dennis Gu (Inactive)
            ndcosta Nelson Dcosta (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: