Problem with RFCLOOKUP

[Former Member]

Hello,

While doing unit testing for an interface using the standard module fm RFCLOOKUP, the PI system (ESR) freezes completely causing the JAVA stack down.

The error in the log shows that the communication channel of the RFCLOOKUP, is using a business system which is not available.  Even though while executing our test the parameter RFCLOOPKUP has the correct business system of the environment we are using.

It has been noticed that the error is being showed many times in the log which results in creating more than 1000 sessions.  This causes the JAVA stack unavailable.

The same test has been repeated several times, the anomaly was produced when the test was executed.

While debugging, the error received when the option queues was displayed for the module function RFC: Cannot perform RFC lookup.

Even though a cache refresh was done, the anomaly was being received.  Whereas, when the JAVA stack was refreshed, the test executed was correct.

The anomaly is being received at random even while doing the test, the parameter RFC lookup is being chosen.

Do you have any idea why when executing the test with the correct parameter for RFCLOOKUP, the system freezes completely and from where the other business service is being picked up which is appearing in the log errors?

Error received:

Error while getting the SystemAccessor Plain exception:Error when calling an adapter by using communication channel (Party:*, Service: <Service>, Object ID: <object ID>) The channel with object ID <object ID> could not be found in the integration Server Java Cache.  Check if the channel exists in the IB directory and execute a refresh of the Java Cache.

com.sap.aii.mapping.lookup.LookupException

com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.getProxy(SystemAccessorInternal.java:<line>)

[bhavesh_kantilal]

What version of PI are you on? On earlier release of PI 7.3, there was a change in the RFC Lookup / SOAP Lookup functionality and it was mandatory to have a Receiver Agreement for the RFC Lookup channel ( Even a Dummy one was Ok ).

It might be worth creating a Receiver Agreement for this RFC Channel if it does not exist and giving this a shot. If it already exists, then probably a OSS to SAP might also help.

One another thing I can think of - set a session BreakPoint in your RFC in ECC and see what happens when the RFC Call is triggered, it could also be a case where the RFC is taking a lot of execution time causing several threads etc..

Regards,

Bhavesh

[Bhargavakrishna]

Hi Lovena,

As suggested by S Tomar remove the channel and re create it and check the cache notifications in ID once you activate the communication channel.

Refer the below blog

&quot;Cannot Perform RFC Lookup&quot; in Production system | SCN

Regards

Bhargava Krishna

[suchitatomar]

Hi Lovena,

Please follow below steps :-

1) check the communication channel is active or not ?

2) check the if the error is resolved by using cache refresh for not

  http://host:port/CPACache/refresh?mode=full    delta

3) if not, remove the communication channel and create again and activate (simple method is copy the cc to cc1, again delete cc, again copy cc1 to cc and activate).

Now resend the failed messages in ABAP stack

Regards

S Tomar