cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP 413 Request Entity Too Large

Former Member
0 Kudos

Hi All,

When we are trying to connect to a target system using SOAP(HTTPS) adapter, we are getting the error as attached. We checked with the target system and they can handle upto 15 MB message size. The error we are encountering is for any thing just above 45-50kb. Please provide your inputs on resolving this issue.

Regards,

Vishal

Accepted Solutions (0)

Answers (2)

Answers (2)

rcsegovia
Active Participant
0 Kudos

Hi Vishal,

My cents: Try to isolate the problem and check if https is working fine with others endpoints.

If yes: I guess the problem should be at endpoint site.

If no: try to reconfigure SAP PI https connection.

good luck,

Roberto.

Former Member
0 Kudos

Hi Roberto,

Thanks for the suggestion. But we have only one system with which we have HTTPS connectivity established. If we have to go for HTTPS with new systems then it is a very lengthy process.

Regards,

Vishal

azharshaikh
Active Contributor
0 Kudos

Hi Vishal,

What is the PI version you are using?

Please check Note # 657759 - "413 Request Entity Too Large" on J2EE Engine if it helps.

Solution

1.Procedure for 6.20 J2EE Engine
The maximum accepted request headers length is customizable. It can be adjusted by the MaxRequestHeadersLength property of http service on dispatcher (if using cluster version), or on the alone node (if using the standalone version). You can change this property to a larger value, or set it to a negative value. The negative value means that no restrictions will be imposed on the request headers length. Setting the above mentioned negative value for MaxRequestHeadersLength is possible for service pack 14 and later of the j2ee engine. If the version you are using is lower, you have to increase the value of the property. Sufficient in this case might be to double the default.
2.Procedure for 6.30/6.40 J2EE Engine
In J2EE Engine 6.30/6.40 the maximum request headers and body length is customizable.
The maximum request length can be adjusted by the property MaxRequestHeadersLength of the Http Provider service on the dispatcher node. You can change this property to a larger value, or set it to a negative value. The negative value means that no restrictions will be imposed on the request headers length.
The maximum body length can be adjusted by changing the value of the property MaxRequestContentLength in the HttpProvider service on the dispatcher node. Again you can increase the value of the property of set it to a negative value, which means that no restrictions are imposed

Refer:

First try to adjust <MaxRequestContentLength> and then Test. If not resolved, then go for <MaxRequestHeadersLength>.

Regards,

Azhar

Former Member
0 Kudos

Thanks for your response,Azhar. I did go through the suggested OSS note before posting in SCN. We are on 7.31.

We are able to send messages using HTTP but not using HTTPS for messages greater than

40kb size.

The parameter icm/HTTP/max_request_size_KB = 102400 i.e. 10MB. So we are still not clear as to where is the issue. Please suggest

Regards,

Vishal

azharshaikh
Active Contributor
0 Kudos

Hi Vishal,

Check if following notes help:

1144149 - TrexException: HTTP server error: 413

1994965 - The enrollment of an iOS Device

1102321 - Explanation of IIS log codes

Regards,
Azhar