java.net.SocketException: Reply from SOCKS server has bad version

hc-httpclient-users | Mark Claassen | 10 years ago
  1. 0

    HttpClient, SOCKS proxy, and webstart

    hc-httpclient-users | 10 years ago | Mark Claassen
    java.net.SocketException: Reply from SOCKS server has bad version
  2. 0

    RE: HttpClient, SOCKS proxy, and webstart

    hc-httpclient-users | 10 years ago | Mark Claassen
    java.net.SocketException: Reply from SOCKS server has bad version
  3. 0

    HttpClient, SOCKS proxy, and webstart

    mail-archive.com | 4 months ago
    java.net.SocketException: Reply from SOCKS server has bad version
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Issue in Jdeveloper

    Oracle Community | 6 months ago | 3254301
    java.net.SocketException: Permission denied: connect

    7 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.net.SocketException

      Reply from SOCKS server has bad version

      at java.net.SocksSocketImpl.connectV4()
    2. Java RT
      Socket.<init>
      1. java.net.SocksSocketImpl.connectV4(Unknown Source)
      2. java.net.SocksSocketImpl.connect(Unknown Source)
      3. java.net.Socket.connect(Unknown Source)
      4. java.net.Socket.connect(Unknown Source)
      5. java.net.Socket.<init>(Unknown Source)
      6. java.net.Socket.<init>(Unknown Source)
      6 frames
    3. HttpClient
      DefaultProtocolSocketFactory.createSocket
      1. org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(Unknown Source)
      1 frame