on 11-04-2015 6:09 AM
Hi All,
We have created a soap to proxy synchronous scenario. the request message is coming from client system to our SAP PI (7.1) and request message goes to Proxy. but the message in sxmb_moni shows in log version
and after sometime gives error. In HTTPError we are getting this error message
- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
</SAP:Error>
In our scenario, if the request contain less invoice (90 unique invoices) in it the message process successfully but only in one payload our scenario is failing. This payload client contains 200 unique invoices which is taking time in ECC for processing.
we also increases the HTTP_timeout setting in smicm and sxmb_adm to 6000000 milli seconds.
We also added XI.Timeout parameter in SOAP Communication channel and value set to 600000.
Hi,
The issue has been resolved .
The workaround done are:
1)
ICM parameter like HTTP Keep Alive = 60 and Proc. TimeOut =900 was maintained in both ECC and PI
2)Proxy Coding was tuned to throw the response within maximum time lag of 2 seconds .
which resolved the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ayush,
Have you checked the transactions smq1 and smq2 if you have any message stuck?
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Inaki,
Yes, I have checked., Everything is fine.
The main issue is when we process the SOAP message which contains nearly 190 unique invoices,while request its fine, it fails for response .
but when I have reduced the Payload to half of size from my SOAP UI tool, its working fine.
My concern is: Is there any Parameter SAP suggest about the Payload size.??
Hi Inaki
The icm/HTTP/max_request_size_KB is 102400 and the EO_MSG_SIZE_LIMIT is not defined in our system.
the screen shot is attached.
Should i need to configure EO_MSG_SIZE_LIMIT
< > according to you the exception is something else, please put some light on that part so that i can also check those stuffs.
Regards,
Ayush
Check the Time out parameter in SXMB_ADM
Hi Ayush,
Follow this note 1929464 - 402 ICM_HTTP_TIMEOUT 500 Connection timed out and try to change PROCTIMEOUT icm parameter or the parameter HTTP_TIMEOUT on the smb_adm transaction.
Regards.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.