MAPPING JCO_COMMUNICATION_FAILURE (SOAP to RFC scenario)

[Former Member]

Hi,

Our system is PI 7.1 EHP1 and the scenario is to SOAP to RFC (Synchronous). I have imported the RFC into ESR and used it as data type for Outbound interface for SOAP.

Initially i havent created any mapping because all Interface fields are same (name and type) with RFC because i have used RFC as data type. When we have tested the integration via SOAPUI we have seen that the request message wasn't transferred to RFC but the response was transferred from RFC to SOAP response. Could it be a bug? or is it normal behaviour?

Later, i have created a graphical mapping without any data conversion etc.. It is just mapping. This time it transferred the request and response as well.

When we have started stress test on a PI system (6000 SAPS), the PI JAVA stack started to use %100 of CPU. We have processed 100 message per minute. After 20 minutes, Java stack of PI has crashed and restarted.

Our plan is to process message more then this test numbers. Possibly it is approx 400 message per minute.

I have found below errors on RWB (approx 250 message have below errors).

How this high CPU consumption can be resolved?

&&&&&&&&&&&&&&&

- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

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

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

<SAP:P1>Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>&quot;COMMUNICATION FAILURE&quot; during JCo call. Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT' : cmRc=2 thRc=67</SAP:Stack>

</SAP:Error>

&&&&&&&&&&&&&&&&&&&&&&&

- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

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

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

<SAP:P1>connection to partner 'loopback:0' broken / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 th</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>&quot;SYSTEM FAILURE&quot; during JCo call. connection to partner 'loopback:0' broken / CPIC-CALL: 'ThSAPCMRCV' : cmRc=20 th</SAP:Stack>

</SAP:Error>

&&&&&&&&

Kind regards,

Altuğ Bayram

[Former Member]

Hi,

For high load scenarios with RFC Adapter, you should set the parameter Max Connections under RFC Client Parameters in the RFC Adapter receiver channel configuration to a pretty high value. This would enable the RFC Adapter to have that many max number of parallel connections. Hope this might help to an extent for your stress test.

For the end to end scenario, try checking the tuning guide and the link sent in the last reply for high performance settings.

Best Regards,

Pratik

[former_member182967]

Hello Pratik,

Do you mean that adjust the following parameter for RFC adapter in Java?

Send.maxConsumers\Recv.maxConsumers\Call.maxConsumers\Rqst.maxConsumers

Regards,

Ning Tong

[Former Member]

Hi,

Connection between ABAP and JAVA has been broken...thats the reason for the JCO_COMMUNICATION Error

you need to either restart the java or have a look at the RFC Connection JCO_AI_CONNECTION...

re you making use of AAE for this scenario..which can improve the performance than using classic scenario.

performance depends on the hardware of the server also...

Check the sizing Guide of the PI 7.1 on SDN.

Check the below link it may help you..

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f0b96675-87cf-2c10-b489-dee0ac03f782

HTH

Rajesh