My Oracle Support Banner

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

Last updated on FEBRUARY 06, 2024

Applies to:

Oracle API Gateway - Version and later
Information in this document applies to any platform.


Currently migrating from Oracle Enterprise Gateway to Oracle API Gateway 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.

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: 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(
  at com.vordel.mime.Body.write(
  at com.vordel.dwe.http.ServerTransaction.sendResponseN(Native Method)
  at com.vordel.dwe.http.ServerTransaction.sendResponse(
  at com.vordel.dwe.http.HTTPPlugin.invokeDispose(
  at com.vordel.dwe.http.HTTPPlugin.invoke(
(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.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

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