Solved: Response Body missing from call to API proxy altho...

deepakomathukat · 12-20-2017 01:27 PM

I have a API proxy that is a straight passthrough. When calling the backend server through Apigee I'm seeing a 200 status being returned but the response body is empty. Network trace proves that backend server is responding with a body.

deepakomathukat

Case 1436673

. Apigee support figured the exception as being caused due to the backend not providing a

‘Content-Length’ or ‘Transfer-Encoding’ header in the response. Turns out the F5 in front of the backend was stripping off the Transfer-Encoding header.

.

View solution in original post

DChiesa

Can you provide a Trace session? Trace what you're seeing, then Download the trace, zip it up, and attach it here.

Report Inappropriate Content

deepakomathukat

tracexml.txt

deepakomathukat

Added the trace

deepakomathukat

Seeing this in the Apigee logs -

NIOThread@1 WARN MESSAGING.FLOW - FlowDebugPoint.invoke() : Exception trying to mask value of payload

java.lang.ClassCastException: java.lang.String cannot be cast to net.minidev.json.JSONObject

at com.apigee.jsonparser.JSONUtil.contentSainity(JSONUtil.java:55) ~[jsonparser-1.0.0.jar:na]

at com.apigee.flow.debug.points.FlowDebugPoint.invoke(FlowDebugPoint.java:139) ~[message-flow-1.0.0.jar:na]

at com.apigee.flow.debug.points.AbstractFlowStateChangePoint.invoke(AbstractFlowStateChangePoint.java:44) [message-flow-1.0.0.jar:na]

at com.apigee.flow.MessageFlowImpl.dispatchToDebugService(MessageFlowImpl.java:575) [message-flow-1.0.0.jar:na]

at com.apigee.flow.MessageFlowImpl.onGoto(MessageFlowImpl.java:378) [message-flow-1.0.0.jar:na]

at com.apigee.flow.MessageFlowImpl.resume(MessageFlowImpl.java:295) [message-flow-1.0.0.jar:na]

at com.apigee.flow.execution.ExecutionContextImpl$1.run(ExecutionContextImpl.java:96) [message-flow-1.0.0.jar:na]

at com.apigee.nio.NIOSelector.runTasks(NIOSelector.java:363) [nio-1.0.0.jar:na]

at com.apigee.nio.NIOSelector.access$000(NIOSelector.java:34) [nio-1.0.0.jar:na]

at com.apigee.nio.NIOSelector$2.findNext(NIOSelector.java:311) [nio-1.0.0.jar:na]

at com.apigee.nio.NIOSelector$2.findNext(NIOSelector.java:302) [nio-1.0.0.jar:na]

at com.apigee.nio.util.NonNullIterator.computeNext(NonNullIterator.java:21) [nio-1.0.0.jar:na]

at com.apigee.nio.util.AbstractIterator.hasNext(AbstractIterator.java:47) [nio-1.0.0.jar:na]

at com.apigee.nio.handlers.NIOThread.run(NIOThread.java:96) [nio-1.0.0.jar:na]

deepakomathukat

tracexml.txt

deepakomathukat

added trace

deepakomathukat

tracexml.txt

Attaching trace . Please disregard the stack trace I provided earlier. That wasn't related to this trace

adevegowda

@Deepa,

I had a look at the trace file provided, and I agree that the Response body is empty.

1. Are you sure that you see response body in the Network trace ? If yes, can you please share the tcpdump ? If you have confidential information, then you can email the tcpdump only to me.

2. Just to re-confirm, if you make a direct call to the backend server from the Message Processor, do you see the response body ?

deepakomathukat

@AMAR DEVEGOWDA

Yes, the response body is present in the network trace. Microservice response was tapped for the call and a valid response body is present. Just an FYI- This is a new Apigee environment and I'm seeing the exact same issue with another proxy as well.

Here is the exception in the logs when additional logging is enabled

2017-12-21 13:54:51,374 org:xyz env:prod api:abc rev:4 messageid:REDACTED-31146-135234-2 NIOThread@1 WARN MESSAGING.FLOW - FlowDebugPoint.invoke() : Exception trying to mask value of payload