HTTP 500 Internal Server Error with Large Attachment in SOAP Scenario

[Former Member]

Hi,

we have implemented SOAP - XI - SOAP Scenario in our landscape (Sap Neatweaver Process Integration 7.1) .

One of the functionality of this scenario is the Upload of Documents to External Web Service through standard SOAP Attachment.

If we try to upload a small file (smaller than 20MB), task works fine and the document is correctly uploaded.

If we try to upload a larger file, we encountered in this generic error:

com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.engine.interfaces.messaging.api.exception.MessagingException: XIAdapterFramework:GENERAL:com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error

at com.sap.aii.adapter.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:1161)

We tried to increase timeout parameters (in communication channel and in ICM Value) but the response is the same.

We verify also if icm/HTTP/max_request_size_KB parameter was set to a value smaller than our file size limit (20MB) but is set to default value (100MB).

The problem isn't on External Web Service Layer because if we try to upload the same documents directly to that web service upload works fine, and in External Web Service's Log there aren''t any indications of this error.

So I ask you: are there any System Parameters to verify to solve this issue?

For additional, in ICM Monitor LOG we can read this WARNING when we call our service:

WARNING => IcmReadFromConn(id=53/454390): temporarily out of MPI buffers -> roll out [icxxthrio_mt 2646]

This warning may be related to the problem? If yes, how can we solve it?

Thanks a lot,

Marcello Ricci

[Former Member]

Hi ,

Please answer my following questiosn.

1) which PI version are you using?

2) How many J2EE nodes you have.

please be reminded that SOAP is not for the heavy messages. Then you need to increase your timeout parameters from BASIS.

Rgds

Veeru

Edited by: viru srivastava on Dec 14, 2010 10:18 PM

[Former Member]

Hi Viru,

we are using PI 7.1 and we have just on J2EE nodes.

Can you explain more in detail what kind of parameters and how we can increase timeout in BASIS?

Thanks a lot

[Former Member]

Hi,

Please go through the below link. It will help you.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03...

Rgds

Veeru

[george_hamilton]

Have you turned on debug for the SOAP adapter?

[Former Member]

Hello George

did you solve this problem?

Thanks a lot

[Former Member]

Hi,

Just download SOAP UI client and test your scenario. It will work. Th esame issue i had facd with ALTOVA TOOL,When i switched to SOPA UI, it worked.

Just try and let me know.

Thanks

Veeru

[Former Member]

Hi Viru,

I just use SoapUI client tool but don't works.

Thanks

Marcello

Edited by: MRicci85 on Dec 14, 2010 5:13 PM

[RKothari]

Hi,

Please refer to SAP Note: 856597 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 SOAP Adapter.

It suggests that you can use the below paramerter to increase timeout for receiver SOAP adapter:

XMBWS.Timeout : Provide value in milliseconds

Also, the trace path is mentioned for PI 7.1 . Please check if any specific error is mentioned.

-Rahul

[Former Member]

Hi Rahul,

thanks for your suggest, but the solution you mentioned is just tested and unfortunately not working.

Edited by: MRicci85 on Dec 14, 2010 3:28 PM

[Former Member]

Hi Marcello,

Ref SAP Note: 804124, 807000

Thanks,