SAP Knowledge Base Article

2508229 - How to handle "Error: (413) Request

Symptom
When processing in PI system, if the size of the processing message is too big, then we may meet an error "
(413)Request Entity Too Large", it can usually be divided into two conditions.

1. Request:
When you make a HTTP request to PI system, when the size of the request entity exceeds a certain value,
you will receive errors something lile below:
"The request entity must be less than <XXX> bytes!"... "Content length must be less than
<XXX> bytes!"...
and you will receive a response code: "413 Request Entity Too Large".

2. Response:
a. When making a HTTP request from PI system to a Web Service using SOAP (Axis) Adapter. When
processing a message of which the size exceeds a certain value, an error "Message processing
failed. Cause: (413)Request Entity Too Large" can be seen in the SOAP (Axis) receiver channel in
Communication Channel Monitoring in NWA. Besides, in Message Monitor in NWA, the errors similar
to the following could be observed:
Error Axis: error in invocation: (413)Request Entity Too Large
Error MP: exception caught with case (413)Request Entity Too Large
Error Exception caught by adapter framework: (413)Request Entity Too Large
Error Transmitting the message to endpoint <local> using connection
SOAP_http://sap.com/xi/XI/System failed, due to:
com.sap.engine.interfaces.messagng.api.exception.MessagingException: (413)Request Entity
Too Large...

Also, the errors in XPI inspector trace with Example 50 similar to the following could be observed:
(413)Request Entity Too Large
at com.sap.aii.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:821)
at com.sap.aii.axis.transport.http.HTTPSender.invoke(HTTPSender.java:180)...

b. When making a HTTP request from PI system to a Web Service using the SOAP Adapter
SOAP: Call failed: java.io.IOException: HTTP Error response for SOAP request or invalid
content-type.; HTTP 413 Request Entity Too LargeHTTP 413 Request Entity Too Large

Environment
SAP NetWeaver 7.0
 SAP enhancement package 1 for SAP NetWeaver 7.0
SAP enhancement package 2 for SAP NetWeaver 7.0
SAP enhancement package 3 for SAP NetWeaver 7.0
SAP NetWeaver Process Integration 7.1
SAP enhancement package 1 for SAP NetWeaver Process Integration 7.1
SAP NetWeaver 7.3
SAP enhancement package 1 for SAP NetWeaver 7.3
SAP NetWeaver 7.4
SAP NetWeaver 7.5

Reproducing the Issue

2. Trigger the SOAP/SOAP (Axis) receiver communication channel with a message which is bigger than a
certain size.

Cause
1. In the first situation, when the HTTP request reach the PI system, the J2EE engine by default imposes a
limit on the size of the request, as a result when the HTTP request exceeds the critical size, the request will
be blocked and response the code "(413)Request Entity Too Large".

2. In the second situation, the cause is that there is a restriction in size of the message in the target Web
Service system, when the size of the sent message exceeds the restriction in the target Web Service
system, the error code (413)Request Entity Too Large will be returned from the target Web Service system.
And then, PI throws the above mentioned error.

3. To trace the situation, see the Note 1904944 (/sap/support/notes/1904944) referenced below.

Resolution
1. In the first situation, you can adjust the value of maximum accepted request headers length and maxium
request body length.
a. For NetWeaver releases 7.0x and lower, you can refer to Note 657759
(/sap/support/notes/657759) "413 request Entity Too Large" on J2EE Engine for more details.
b. For NetWeaver releases 7.10 and higher, set the ICM parameter icm/<PROT>/max_request_size_KB
(https://help.sap.com/viewer/bd78479f4da741a59f5e2a418bd37908/7.5.9/en-
US/483e87b3ca6b72d0e10000000a42189c.html) to a sufficiently high value

2. In the second situation, we advise you to contact the vendor/owner of the target Web Service to find out the
restriction in the target Web Service and then adjust the restriction value. As the message is successfully
sent out from SAP PI, the restriction is coming from the third party Web Service side. They may be able to
increase the value to allow the request go through.
 See Also
SAP Note 1514898 (/sap/support/notes/1514898) XPI Inspector for troubleshooting XI
SAP Note 1904944 (/sap/support/notes/1904944) Client side HTTP tracing for SAP PI receiver adapters

SAP Community: HTTP tracing in SOAP receiver adapters with TraceHTTP module parameter
(https://blogs.sap.com/2015/10/26/http-tracing-in-soap-receiver-adapters-with-tracehttp-module-parameter/)
SAP Community: HTTP 413 Request Entity Too Large (https://archive.sap.com/discussions/thread/3671129)

Keywords
(413)Request Entity Too Large, Web Service, Request, Size, SOAP Axis, Receiver, Communication channel,
MessagingException, Response, XIAdapter, SOAP_EXCEPTION, Process Integration 7.0, PI 7.0, PI 7.01, PI 7.02,
Process Integration 7.10, PI 7.10, Process Integration 7.11, PI 7.11, Process Integration 7.30, PI 7.30, Process
Integration 7.31, PI 7.31, Process Orchestration 7.4, PI 7.4, PO 7.4, Process Orchestration 7.5, PI 7.5, PO 7.5, XI,
AEX

Products
Products

SAP NetWeaver 7.0

SAP NetWeaver 7.1

SAP NetWeaver 7.2

SAP NetWeaver 7.3

SAP NetWeaver 7.4

SAP NetWeaver 7.5

SAP enhancement package 1 for SAP NetWeaver 7.0

SAP enhancement package 1 for SAP NetWeaver 7.3

SAP enhancement package 2 for SAP NetWeaver 7.0

SAP enhancement package 3 for SAP NetWeaver 7.0

This document refers to

657759 "413 Request Entity Too Large" on J2EE Engine (/sap/support/notes/657759)

1904944 Client side HTTP tracing for PI SOAP receiver adapter (/sap/support/notes/1904944)
1514898 XPI Inspector for troubleshooting SAP Process Orchestration / Integration
(/sap/support/notes/1514898)

icm/HTTP/max_request_size_KB
(https://help.sap.com/viewer/bd78479f4da741a59f5e2a418bd37908/7.5.9/en-
US/483e87b3ca6b72d0e10000000a42189c.html)

HTTP 413 Request Entity Too Large (https://archive.sap.com/discussions/thread/3671129)

HTTP tracing in SOAP receiver adapters with TraceHTTP module parameter

This document is referenced by

()