org.apache.http.NoHttpResponseException: localhost:9001 failed to respond

Mirth Project | Nick Rupley | 9 months ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    It appears this was caused by the updated version of Apache HttpComponents HttpClient we're using (4.5.1). If the server drops a connection, the client may not be aware of it until it actually tries to use the socket. Apparently the newer version does not automatically check for server-side closures, so if you send a message a while after the server has closed its side, you'll get something like this: {code}HTTP Sender error ERROR MESSAGE: Error connecting to HTTP server org.apache.http.NoHttpResponseException: localhost:9001 failed to respond at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:143) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57) at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:261) at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:165) at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:272) at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:124) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:271) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71) at com.mirth.connect.connectors.http.HttpDispatcher.send(HttpDispatcher.java:318) at com.mirth.connect.donkey.server.channel.DestinationConnector.handleSend(DestinationConnector.java:778) at com.mirth.connect.donkey.server.channel.DestinationConnector.process(DestinationConnector.java:437) at com.mirth.connect.donkey.server.channel.DestinationChain.doCall(DestinationChain.java:121) at com.mirth.connect.donkey.server.channel.DestinationChain.call(DestinationChain.java:63) at com.mirth.connect.donkey.server.channel.Channel.process(Channel.java:1706) at com.mirth.connect.donkey.server.channel.Channel.dispatchRawMessage(Channel.java:1189) at com.mirth.connect.donkey.server.channel.SourceConnector.dispatchRawMessage(SourceConnector.java:192) at com.mirth.connect.server.controllers.DonkeyEngineController.dispatchRawMessage(DonkeyEngineController.java:1052) at com.mirth.connect.server.api.servlets.MessageServlet$2.run(MessageServlet.java:106) at java.lang.Thread.run(Thread.java:745){code}

    Mirth Project | 9 months ago | Nick Rupley
    org.apache.http.NoHttpResponseException: localhost:9001 failed to respond
  2. 0

    It appears this was caused by the updated version of Apache HttpComponents HttpClient we're using (4.5.1). If the server drops a connection, the client may not be aware of it until it actually tries to use the socket. Apparently the newer version does not automatically check for server-side closures, so if you send a message a while after the server has closed its side, you'll get something like this: {code}HTTP Sender error ERROR MESSAGE: Error connecting to HTTP server org.apache.http.NoHttpResponseException: localhost:9001 failed to respond at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:143) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57) at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:261) at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:165) at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:272) at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:124) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:271) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71) at com.mirth.connect.connectors.http.HttpDispatcher.send(HttpDispatcher.java:318) at com.mirth.connect.donkey.server.channel.DestinationConnector.handleSend(DestinationConnector.java:778) at com.mirth.connect.donkey.server.channel.DestinationConnector.process(DestinationConnector.java:437) at com.mirth.connect.donkey.server.channel.DestinationChain.doCall(DestinationChain.java:121) at com.mirth.connect.donkey.server.channel.DestinationChain.call(DestinationChain.java:63) at com.mirth.connect.donkey.server.channel.Channel.process(Channel.java:1706) at com.mirth.connect.donkey.server.channel.Channel.dispatchRawMessage(Channel.java:1189) at com.mirth.connect.donkey.server.channel.SourceConnector.dispatchRawMessage(SourceConnector.java:192) at com.mirth.connect.server.controllers.DonkeyEngineController.dispatchRawMessage(DonkeyEngineController.java:1052) at com.mirth.connect.server.api.servlets.MessageServlet$2.run(MessageServlet.java:106) at java.lang.Thread.run(Thread.java:745){code}

    Mirth Project | 9 months ago | Nick Rupley
    org.apache.http.NoHttpResponseException: localhost:9001 failed to respond
  3. 0

    GitHub comment 189#146611801

    GitHub | 1 year ago | maksimu
    org.apache.http.NoHttpResponseException: db-shared-epsilon-1207.myserverhere.com:4166 failed to respond
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    general - Bug#805813: llvm-toolchain-3.4 ftbfs with ISL 0.15 - msg#01908 - Recent Discussion OSDir.com

    osdir.com | 11 months ago
    org.apache.http.NoHttpResponseException: 127.0.0.1:50925 failed to respond at __randomizedtesting.SeedInfo.seed([4EE3FEA531BBACFC:5988511AA53B2E6E]:0)
  6. 0

    com.github.ywilkof.sparkrestclient.FailedSparkRequestException: org.apache.http.NoHttpResponseException: ipaddress:6066 failed to respond

    GitHub | 2 months ago | berrytchaks
    com.github.ywilkof.sparkrestclient.FailedSparkRequestException: org.apache.http.NoHttpResponseException: 192.168.0.121:6066 failed to respond
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. org.apache.http.NoHttpResponseException

    localhost:9001 failed to respond

    at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead()
  2. Apache HttpClient
    DefaultHttpResponseParser.parseHead
    1. org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:143)
    2. org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57)
    2 frames
  3. Apache Http
    HttpRequestExecutor.execute
    1. org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:261)
    2. org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:165)
    3. org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:272)
    4. org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:124)
    4 frames
  4. Apache HttpClient
    CloseableHttpClient.execute
    1. org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:271)
    2. org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
    3. org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
    4. org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
    5. org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
    6. org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:71)
    6 frames
  5. com.mirth.connect
    MessageServlet$2.run
    1. com.mirth.connect.connectors.http.HttpDispatcher.send(HttpDispatcher.java:318)
    2. com.mirth.connect.donkey.server.channel.DestinationConnector.handleSend(DestinationConnector.java:778)
    3. com.mirth.connect.donkey.server.channel.DestinationConnector.process(DestinationConnector.java:437)
    4. com.mirth.connect.donkey.server.channel.DestinationChain.doCall(DestinationChain.java:121)
    5. com.mirth.connect.donkey.server.channel.DestinationChain.call(DestinationChain.java:63)
    6. com.mirth.connect.donkey.server.channel.Channel.process(Channel.java:1706)
    7. com.mirth.connect.donkey.server.channel.Channel.dispatchRawMessage(Channel.java:1189)
    8. com.mirth.connect.donkey.server.channel.SourceConnector.dispatchRawMessage(SourceConnector.java:192)
    9. com.mirth.connect.server.controllers.DonkeyEngineController.dispatchRawMessage(DonkeyEngineController.java:1052)
    10. com.mirth.connect.server.api.servlets.MessageServlet$2.run(MessageServlet.java:106)
    10 frames
  6. Java RT
    Thread.run
    1. java.lang.Thread.run(Thread.java:745)
    1 frame