on 10-21-2009 6:59 PM
Hi Experts,
We are testing a simple Proxy(ECC) to File scenario in QA. This interface was working fine in Dev but we are getting the following error here in QA:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!-- Call Adapter -->
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">OK_BUT_NO_XI_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>HTTP Status Code 200 Received But Error During Response Parsing: No XI Response Received XML element Envelope missing in SOAP message header (SAP XI Extension)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
We searched other threads but could not get any solution. Please provide suggestions.
Thank You.
Regards,
Anandan
Hi,
This thred is very helpful to me.
Because, I'm facing same situation.
I did the following config.
> increase the value of icm/HTTP/max_request_size_KB to 512MB
> icm/wp_roll_timeout to maximum
> HTTP TIMEOUT to 1800 sec
> icm/wp_roll_timeout to maximum
> mpi/total_size_MB to maximum
> mpi/buffer_size to maximum
But I don't know how to config the followings and which tool I have to use.
> and then increased the maxthreadcount ,maxcontentlength using config tool...
> and also increased the java heap size to maximum....
Could you tell me how to, please.
Shinya Kawagoe
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the problem has been resolved
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please check if all the parameter configurations are done correctly for receiving a message through proxy. Check if you are receiving proper data from the proxy in the first case. I guess this has to do mostly with the settings.
Thanks and Regards,
Sarath.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
the problem was due to high volume message (247 MB ) ...Java stack was not able to process this huge message ,that is the reason ,it started automatically and as a result , "HTTP Status Code 200 Received But Error During Response Parsing" due to unavailability of AFW during Call adapter step in the pipeline processing...
We have done the following activities in order to solve this problem....
increase the value of icm/HTTP/max_request_size_KB to 512MB
icm/wp_roll_timeout to maximum
HTTP TIMEOUT to 1800 sec
icm/wp_roll_timeout to maximum
mpi/total_size_MB to maximum
mpi/buffer_size to maximum
and then increased the maxthreadcount ,maxcontentlength using config tool...
and also increased the java heap size to maximum....
After doing everything ,the file has been successfully processed....
the problem has been resolved...
User | Count |
---|---|
82 | |
9 | |
9 | |
7 | |
7 | |
7 | |
7 | |
6 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.