com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: java.net.NoRouteToHostException: No route to host

mirthcorp.com | 4 months ago
  1. 0

    [MIRTH-3708] Web Service dispatcher does not queue on SocketExceptions - Mirth Project

    mirthcorp.com | 4 months ago
    com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: java.net.NoRouteToHostException: No route to host
  2. 0

    The question is, do it should? Someone received the following NoRouteToHostException which is a SocketException. From what I've seen this may be caused by firewall issues which is not really something that's meant to be temporary. The queue is intended to be for recoverable errors and if a firewall rule is in place it's not going to make a difference how many times the connector attempts to send the message. This one is probably in a gray area and I'd be curious what actual circumstances this occurs in. Javadocs (https://docs.oracle.com/javase/7/docs/api/java/net/NoRouteToHostException.html) indicate that "Typically, the remote host cannot be reached because of an intervening firewall, or if an intermediate router is down." The second example could be a valid use case for queueing. {code} Web Service Sender error ERROR MESSAGE: Error invoking web service com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: java.net.NoRouteToHostException: No route to host                 at com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:117)                 at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:208)                 at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:130)                 at com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:124)                 at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:1121)                 at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:1035)                 at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:1004)                 at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:862)                 at com.sun.xml.internal.ws.client.Stub.process(Stub.java:448)                 at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:250)                 at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:289)                 at com.mirth.connect.connectors.ws.WebServiceDispatcher.send(WebServiceDispatcher.java:479)                 at com.mirth.connect.donkey.server.channel.DestinationConnector.handleSend(DestinationConnector.java:747)                 at com.mirth.connect.donkey.server.channel.DestinationConnector.run(DestinationConnector.java:636)                 at java.lang.Thread.run(Thread.java:745) Caused by: java.net.NoRouteToHostException: No route to host                 at java.net.PlainSocketImpl.socketConnect(Native Method)                 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)                 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)                 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)                 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)                 at java.net.Socket.connect(Socket.java:589)                 at java.net.Socket.connect(Socket.java:538)                 at sun.net.NetworkClient.doConnect(NetworkClient.java:180)                 at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)                 at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)                 at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:275)                 at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:371)                 at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191)                 at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1147)                 at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:998)                 at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177)                 at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1282)                 at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1257)                 at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:250)                 at com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:104)                 ... 14 more {code}

    Mirth Project | 2 years ago | Wayne Huang
    com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: java.net.NoRouteToHostException: No route to host
  3. 0

    The question is, do it should? Someone received the following NoRouteToHostException which is a SocketException. From what I've seen this may be caused by firewall issues which is not really something that's meant to be temporary. The queue is intended to be for recoverable errors and if a firewall rule is in place it's not going to make a difference how many times the connector attempts to send the message. This one is probably in a gray area and I'd be curious what actual circumstances this occurs in. Javadocs (https://docs.oracle.com/javase/7/docs/api/java/net/NoRouteToHostException.html) indicate that "Typically, the remote host cannot be reached because of an intervening firewall, or if an intermediate router is down." The second example could be a valid use case for queueing. {code} Web Service Sender error ERROR MESSAGE: Error invoking web service com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: java.net.NoRouteToHostException: No route to host                 at com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:117)                 at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:208)                 at com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:130)                 at com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:124)                 at com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:1121)                 at com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:1035)                 at com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:1004)                 at com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:862)                 at com.sun.xml.internal.ws.client.Stub.process(Stub.java:448)                 at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:250)                 at com.sun.xml.internal.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:289)                 at com.mirth.connect.connectors.ws.WebServiceDispatcher.send(WebServiceDispatcher.java:479)                 at com.mirth.connect.donkey.server.channel.DestinationConnector.handleSend(DestinationConnector.java:747)                 at com.mirth.connect.donkey.server.channel.DestinationConnector.run(DestinationConnector.java:636)                 at java.lang.Thread.run(Thread.java:745) Caused by: java.net.NoRouteToHostException: No route to host                 at java.net.PlainSocketImpl.socketConnect(Native Method)                 at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345)                 at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)                 at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)                 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)                 at java.net.Socket.connect(Socket.java:589)                 at java.net.Socket.connect(Socket.java:538)                 at sun.net.NetworkClient.doConnect(NetworkClient.java:180)                 at sun.net.www.http.HttpClient.openServer(HttpClient.java:432)                 at sun.net.www.http.HttpClient.openServer(HttpClient.java:527)                 at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:275)                 at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:371)                 at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191)                 at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1147)                 at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:998)                 at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177)                 at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1282)                 at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1257)                 at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:250)                 at com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:104)                 ... 14 more {code}

    Mirth Project | 2 years ago | Wayne Huang
    com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: java.net.NoRouteToHostException: No route to host
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    JAX-WS Java client, WCF service interoperability: "400: Bad Request"

    Stack Overflow | 5 years ago | user1230890
    com.sun.xml.internal.ws.client.ClientTransportException: The server sent HTTP status code 400: Bad Request
  6. 0

    Mirth and WCF: "400: Bad Request" - Mirth Community

    mirthcorp.com | 8 months ago
    com.sun.xml.internal.ws.client.ClientTransportException: The server sent HTTP status code 400: Bad Request

    2 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. com.sun.xml.internal.ws.client.ClientTransportException

      HTTP transport error: java.net.NoRouteToHostException: No route to host

      at com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput()
    2. Java RT
      DispatchImpl.invoke
      1. com.sun.xml.internal.ws.transport.http.client.HttpClientTransport.getOutput(HttpClientTransport.java:117)
      2. com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:208)
      3. com.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:130)
      4. com.sun.xml.internal.ws.transport.DeferredTransportPipe.processRequest(DeferredTransportPipe.java:124)
      5. com.sun.xml.internal.ws.api.pipe.Fiber.__doRun(Fiber.java:1121)
      6. com.sun.xml.internal.ws.api.pipe.Fiber._doRun(Fiber.java:1035)
      7. com.sun.xml.internal.ws.api.pipe.Fiber.doRun(Fiber.java:1004)
      8. com.sun.xml.internal.ws.api.pipe.Fiber.runSync(Fiber.java:862)
      9. com.sun.xml.internal.ws.client.Stub.process(Stub.java:448)
      10. com.sun.xml.internal.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:250)
      11. com.sun.xml.internal.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:289)
      11 frames
    3. com.mirth.connect
      DestinationConnector.run
      1. com.mirth.connect.connectors.ws.WebServiceDispatcher.send(WebServiceDispatcher.java:479)
      2. com.mirth.connect.donkey.server.channel.DestinationConnector.handleSend(DestinationConnector.java:747)
      3. com.mirth.connect.donkey.server.channel.DestinationConnector.run(DestinationConnector.java:636)
      3 frames