Large (>10MB) SOAP Responses Are Truncated in Oracle API Gateway (Doc ID 2245235.1)

Last updated on FEBRUARY 06, 2024

Applies to:

Symptoms

Currently migrating from Oracle Enterprise Gateway 11.1.1.6.1 to Oracle API Gateway 11.1.2.4.0 SP4. After the upgrade, there is an issue with a service that returns a very large XML payload. 

When the response is returned from OAG, it is truncated to 10MB and the remaining data is discarded. 

The following error is seen in the gateway trace file.

ERROR
-----------------------
FATAL  [<THREAD ID>] Failed relaying content (con=<CONNECTION ID>,endpoint=<HOST>:<PORT>,bio=0xXXXXXX max read/write len reached 10485760)
ERROR  [<THREAD ID>] java error 7713 writing response:
java.io.IOException: con=<CONNECTION ID>,endpoint=<HOST>:<PORT>,bio=0xXXXXXX max read/write len reached 10485760
  at com.vordel.dwe.NativeContentSource.relayN(Native Method)
  at com.vordel.dwe.NativeContentSource.relay(NativeContentSource.java:39)
  at com.vordel.mime.Body.write(Body.java:377)
  at com.vordel.dwe.http.ServerTransaction.sendResponseN(Native Method)
  at com.vordel.dwe.http.ServerTransaction.sendResponse(ServerTransaction.java:36)
  at com.vordel.dwe.http.HTTPPlugin.invokeDispose(HTTPPlugin.java:462)
  at com.vordel.dwe.http.HTTPPlugin.invoke(HTTPPlugin.java:143)
(connection closed at )

NOTE: any reference to <HOST>:<PORT> should be replaced with the connection URL being used in whatever environment the problem is being seen.

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.