cancel
Showing results for 
Search instead for 
Did you mean: 

JCO_COMMUNICATION_FAILURE

Former Member
0 Kudos

Hello,

We are trying a small sceanrio,

FILE>XI>IDOC ADAPTER-->R/3 system.

in SXMB_MONI we are getting following Error for message.

Is this has anything to do with program ID?

<?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="">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="MAPPING">JCO_COMMUNICATION_FAILURE</SAP:Code>

<SAP:P1>Error opening an RFC connection.</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>&quot;COMMUNICATION FAILURE&quot; during JCo call. Error opening an RFC connection.</SAP:Stack>

<SAP:Retry>A</SAP:Retry>

</SAP:Error>

Can someone assist in this manner?

Thanks million..in advance

Deepti

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Deepti,

Did you find a solution to this problem? We are having the same issue with IDOC adapter. (RFC error in "Request message mapping" step). Our message mapping is very simple, and does not contain any extra JAVA functions.

brian_arthern2
Participant
0 Kudos

Hi,

We have the same problem. It seems to occur when the system is under high load.

Any solutions to this would be appreciated!

Thanks

Brian

Former Member
0 Kudos

Hi, I guess that by now you might have solved tthe problem, but I'll tell you that usually tuning up the memory settings on the VM gives good solutions. Usually this error indicates too much load on the system, so you can have a look at the different notes that provide assistance on the memory settings, according to your operating system.

Former Member
0 Kudos

Hi,

Are you performing any direct JCO call to XI/R3 though a (custom defined JAVA function) from the mappings?

If that's the case then you first should look at the source of this JCO call and make sure you r using the correct JCO parameters (account details, system information, etc...)

Cheers,

Rob.

Message was edited by: Rob Viana