INITIAL_JCO_RETURN
Hi All
We are facing a problem whenever we test our scenario (IDOC to File). Whenever the payload is of smaller size the scenario works fine, but whenever the load becomes high, then we get the following error in our Monitor,
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">INITIAL_JCO_RETURN</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>All JCo return parameters are initial</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can anybody recommend some solution for this issue, as what are the settings we need to do inorder to overcome this problem. I did check the thread,
Error - "All JCo return parameters are initial"
and we are not transporting any object while testing this scenario.
Just to add we are using XSLT mapping, we do know that XSLT has a problem with memory when the source file is huge, but the complexity of the mapping was what made us to choose XSLT.
regards
Sameer
Hi,
I think this is probably caused by incorrect memory settings, I would strongly suggest you to make sure these are ok. Do you see any outofmemory erros in the logs?
Have a look at the performance header in the sxmb_moni for the relevant message. You can see here how much time did it take the JCO to transfer the data from the abap side and back.
I repeat, please check your memory settings..
Regards, jaime
Similar Messages
-
XI Error Mapping: INITIAL_JCO_RETURN
I have an inbound with this mapping error I've never seen before. I've seen Mapping:EXCEPTION_DURING_EXECUTE, but never INITIAL_JCO_RETURN.
What does this mean?Tom,
It says that you have problems with your mapping. Check you mapping with the help of this weblog:
/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios
Regards,
---Satish -
INITIAL_JCO_RETURN -error in mapping
Hello!
I get the following error in XI when I'm trying to send quite large IDOC in IDOC to JDBC -scenario.
<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="MAPPING">INITIAL_JCO_RETURN</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>All JCo return parameters are initial</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
When I use smaller IDOC in same scenario, it works fine.
Could somebody help me. Is there something wrong with the configuratios or parameters, which could cause this?
Thanks in advance,
JanneHI,
This kind of error occurs when there will be huge data processing across Mapping. Your memmory consumption is being affected due to this processing.
You need to have either optimization of Mapping object or the logice incporporated in mapping and may require to include SAP notes for the performance aspects.
Else try to send the IDOC segments in small chunks
Thanks
swarup
Edited by: Swarup Sawant on Jun 12, 2008 11:44 AM -
All JCo return parameters are initial
Hi,
I'm getting "All JCo return parameters are initial" on a SOAP->XI->R/3 scenario. What could be the cause? This is not all the time, it's working 99.5% of the time!
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">INITIAL_JCO_RETURN</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>All JCo return parameters are initial</SAP:Stack>
<SAP:Retry>N</SAP:Retry>
</SAP:Error>
Rgds,
YvesThanks for your response, I will check with SAP. This is not acceptable! There are lots of traffic in our R/3 world between QAT and PRD. I cannot just stop the messages (XI to PRD) when it's happening. This is really strange. I'm sure there is a way to fix this. I will get back to you when I will find the way.
Thanks
Yves
Maybe you are looking for
-
Basic rundown of my problem. I went to click on Safari, the application bounced once in the dock and acted as if it was opening -- Safari name was in the menu bar on the top of the screen, but no browser window every opened. After a short while, the
-
Is it possible to return the PO number after successful webadi upload
Hi All, Kindly help me for the below scenario if possible. I am downloading approved requisitions through WebADi and then user is adding pay items in the excel of WebADI. Once upload i am submitting the custom concurrent program which indeed submits
-
Hai.. Please tell me the table to find out the history of changes in sale order. Thanks.
-
Camera shows color flashes
-
RFQ Workflow: Agent assignment
Dear All, We are working on the Release RFQ workflow. Per my understanding, the IMG settings determine the users/OUs who should be receiving mails to release the RFQ. This multilevel approval is in place. Now, I have created an RFQ, this triggered th