Skip to Content
avatar image
Former Member

JCO_SYSTEM_FAILURE and J2EE restart

Hi All,

We are currently encountering an issue with IDOC to HTTPS scenario that we we are working on. There are several RFC that are being performed in the mapping to retrieve information from R/3. The mapping has been tested sufficently with data from R/3 DEV system without any issues.

We have the scenario tested in DEV, and its works fine. But when we test the same onjects connected to REL r/3 system, we are noticing that the messages always get stuck in the outbound queue with the status as "transaction executing". After a while the below message is logged:

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_SYSTEM_FAILURE</SAP:Code>

<SAP:P1>Bean SMPP_CALL_JAVA_RUNTIME3 not found on host albbir1, ProgId=AI_RUNTIME_BIR: P</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>&quot;SYSTEM FAILURE&quot; during JCo call. Bean SMPP_CALL_JAVA_RUNTIME3 not found on host albbir1, ProgId=AI_RUNTIME_BIR: P</SAP:Stack>

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

</SAP:Error>

There seems to be an issue with RFC communication, but we can't seem to find the problem. This above error is logged a number of time, after which the J2ee server process will either restart or stop. We have been manually restarting the J2ee server and the cancelling the message with errors.

We have tested the TCP RFC Destination AI_RUNTIME_JCOSERVER, it works fine, before the mesages get stuck.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Dec 31, 2009 at 01:45 PM

    Would you please check INTEGRATION_DIRECTORY_HMI rfc is working fine?

    I presume both rfcs AI_RUNTIME_JCOSERVER & AI_DIRECTORY_JCOSERVER

    If above 3 rfcs works fine...then I suggest you to perform CPACache full refresh using below URL

    http://<PI Server name>:<HTTP Port>/CPACache/refresh?mode=full

    Regards

    Sekhar

    Add comment
    10|10000 characters needed characters exceeded

  • Dec 31, 2009 at 06:04 PM

    Hi Harleen,

    This kind of issue occurs for many cases.

    First of all, if there is a server restart(in specific the java stack) and during that time, if any synchronous interface was in execution it would fail with this error.

    Since, it is a HTTP adapter at the receiver side, it can also occur if the connection is down at the receiver side.

    Because of an untimed restart of a server node/cluster, async interfaces could also fail with this error.

    As of now to clear that issue, you can save the payload and delete the blocked message from the queue and check if other messages are getting processeed on not.

    Check if the connections to target system are working fine.

    Regards,

    Younus

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 02, 2010 at 08:27 AM

    Hi Harleen,

    If there is problem with Program ID register in RFC destination i.e. AI_RUNTIME_BIR... better to re-create it and also restart the PI server.

    Another thing u can do....logged to Visual Administrator with J2EE_ADMIN , Services-> JCo RFC Provider, In the Right hand u will find the RFC Destination AI_RUNTIME_<SID>. Select the destination and click on Stop and then start it again....

    Hope this will help u...

    Regds,

    Pinangshuk.

    Add comment
    10|10000 characters needed characters exceeded