JCO_SYSTEM_FAILURE

[Former Member]

Hi All

on production server everyday we are facing a problem, that a lots of messages stuck in Inbound Queue with queue status SYSFAIL

inside queue after executing LUW, Inside the message i can see the error log

MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>

<SAP:P1>Transaction system failure in method processFunction.</SAP:P1>

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>&quot;SYSTEM FAILURE&quot; during JCo call. Transaction system failure in method processFunction.</

These message goes clear after locking and unlocking of the queue

Any solution for this error ?

Thanks

Sandeep Sharma

[Former Member · Accepted solution]

Hi Sandeep,

If u have checked the prateek reply.In addition with that.This type of error happens when Abap stack and Java stack unable to connect through communication channel.

first you start the communication channel through RWB or ID.

Then ping the server through SM49.

let me know with your result.

Regards,

Sumit Gupta

[Former Member · Accepted solution]

Hi Sumit

very nice to have input from you

you are right that JCO_SYSTEM_FAILURE error generally happens when Abap stack and Java stack unable to connect through communication channel.

but here the error is due to Transaction system failure in method processFunction

So starting CC is not the solution of my problem.

for this error definitly i am doing some mistake in My RFC

anyway thanks for ur input

Regards

sandeep Sharma

[Former Member · Accepted solution]

Hi Sandeep,

I have searched form one SAP note 565196.

Symptom

in XI the Repository can be defined over

the Property of com.sap.aii.additionalmappingtypes additional Mappingtypen

.

With an Cache update are made a replication to Repository and directory data

in run time tables. Here the additional

Mappingtypen is wrongly transferred, so that Mappings of the types concerned

are not implemented.

Further terms

Exchange Infrastructure, XI, Mapping, partner Mapping

a cause and conditions

the problem exists only, if in the Repository over the Property

of com.sap.aii.additionalmappingtypes zusätziche Mappingtypen

were defined and Mappings were put on, which use these

types.

Solution

the problem is repaired in SP0.

Makes a replication to run time tables. Here the additional

Mappingtypen is wrongly transferred, so that Mappings of the types concerned

are not implemented.

Regards,

Sumit Gupta

[Former Member]

Hey,

JCO communication error.

This exception occurs whenever the system is under heavy load. Try tuning up the memory settings on the VM, to help overcome this problem.

Even chk with this

1. go to TCODE: SWEL and check if you have any errors over there

2. go to TCODE: SWF_XI_CUSTOMIZING

maintaint runtime environment

regards,

Milan

[Former Member]

Hi All

thanks for your valuable inputs But keep an eye that i have said that this error occurs on production server so starting server is not an advisable solution for this problem every time.

because restarting server is not a child's play in terms of business loss.

I am looking for a permanent solution for this.

regards

Sandeep Sharma

[SudhirT]

Hi Sandeep,

Check in SM58 of XI and R3 system, you will get some errors related to connection failure with target system. If this is the case that means for a while either the target system was down or there was some network problem or XI system itself was not completely up ie. Java instance was down for some time.

Check what is the issue in your case.

Thanks!

[varun_k]

Hi Sandeep,

When ever this error occurs, I observed most of the times... restarting the server would be a possible solution. As others said Restart the server once and check.

Regards,

Varun

[sunil_singh13]

Hi Sandeep,

Abap Stack establishes connection with Java stack using JCO Connection. If this Connection fails then we get JCO_SYSTEM_FAILURE error.

There could be many reasons for this Like :

1) Your RFC is not getting executed or behaving in unexpected way(some unexpected behaviour is happing for the perticular set of data )

2) Your Message maaping taking longer time to execute.

You are getting SYSFAIL because your BPM is waiting for a message which is yet not reached to BPM and timeout has occured or may be some correlation problem, The correlated message is yet not received.

Restart the server is another option other than suggested by Prateek.

Thanks

Sunil Singh

[Former Member]

Hi !

1 )do a test connection of destination AI_RUNTIME_JCOSERVER

using transaction SM59 and see if it is OK...

2). delete: AI_RUNTIME_JCOSERVER

and re-create it again with the same values

3). restart the XI

Regards

Abhishek

[prateek]

Test RFC destination AI_RUNTIME_JCOSERVER. You may delete and recreate it.

Regards,

Prateek