The most informative information in the snip of log you provided is
2018-09-25 07:19:03,802 org:abcdef env:prod api:rsapassthrough rev:1 messageid:abcdef-99036-2181790-1 NIOThread@1 ERROR HTTP.CLIENT - HTTPClient$Context$3.onException() : SSLClientChannel[C:23.101.157.243:443 Remote host:1.2.3.4:44562]@591217 useCount=7 bytesRead=0 bytesWritten=3069 age=35103ms lastIO=20ms lastIO=20ms isOpen=true.onExceptionRead exception: {}
java.io.EOFException: eof unexpected
at com.apigee.nio.channels.PatternInputChannel.doRead(PatternInputChannel.java:45) ~[nio-1.0.0.jar:na]
at com.apigee.nio.channels.InputChannel.read(InputChannel.java:103) ~[nio-1.0.0.jar:na]
at com.apigee.protocol.http.io.MessageReader.onRead(MessageReader.java:79) ~[http-1.0.0.jar:na]
at com.apigee.nio.channels.DefaultNIOSupport$DefaultIOChannelHandler.onIO(NIOSupport.java:51) [nio-1.0.0.jar:na]
at com.apigee.nio.handlers.NIOThread.run(NIOThread.java:164) [nio-1.0.0.jar:na]
2018-09-25 07:19:03,802 org:abcdef env:prod api:rsapassthrough rev:1 messageid:abcdef-99036-2181790-1 NIOThread@1 INFO HTTP.CLIENT - HTTPClient$Context.logContextDetails() : Request details : host=abcdef path=/AdaptiveAuthentication/services/AdaptiveAuthentication method=POST. Channel details : Bytes read=0
2018-09-25 07:19:03,802 org:abcdef env:prod api:rsapassthrough rev:1 messageid:abcdef-99036-2181790-1 NIOThread@1 ERROR ADAPTORS.HTTP.FLOW - AbstractResponseListener.onException() : AbstractResponseListener.onError(HTTPResponse@3068428d, eof unexpected)
What that tells me is: The Apigee Edge MP is trying to read a response, and is getting nothing. It has bytesRead=0, which means no response at all.
The "other end", aka upstream, aka target server, is not sending a response.
This symptom, this log message, does not indicate a problem in the Apigee Edge MP. If the other end hangs up immediately upon receiving an inbound request, the error logged in the MP log is what we would expect to see. This might happen if there is an error in the request handling code on the backend service. Apigee Edge is just logging the event.
To diagnose this you need to correlate the exceptions seen at the MP with the handling service at the backend.
Look into this endpoint on the backend:
host=abcdef path=/AdaptiveAuthentication/services/AdaptiveAuthentication method=POST
It's curious that the error has occurred at age=35103ms .
Do the other exceptions also timeout at 35s? Do you have a timeout set somewhere in your system to be 35s ? A timeout enforced by Apigee Edge would result in a different error message - it would explicitly state that the connection has timed out. This is not what is happening in your case.
In your case Apigee Edge is trying to read the response and is getting no response. No bytes. It's possible, and seems more likely, that the remote end has timed out at 35s and just didn't respond. This is especially likely if you find the other messages in the MP log all indicate an age of just over 35s.
LinkedIn
Twitter
