Integrated Configurations com.sap.engine.interfaces.messaging.api.exception

[Former Member]

Hi guys,

we are using PI 7.11.

With this release local processing on the advanced adapter engine is possible, when using integrated configurations.

This works fine.

Lately I faced an error situation in an RFC to JDBC scenario, when one field doesn´t meet the conditions of the database.

I tried to dig deeper to identify the incorrect value by switch on the trace in the receiver JDBC channel, as I did several times before.

Afterwards I treied to restart the message.

Following error occurs.

com.sap.engine.interfaces.messaging.api.exception.ConfigException: Unable to retrieve interface determination with object ID ab1bf720bf2711dea7d2020000000030 from CPA cache.

I made some test with integrated configurations (FTP to FTP) and come to the result that errors, which require changes on the communication channel e.g. wrong password etc. result in an new object in the CPA cache

trying restart the failed message ends up in the error specified aboce.

Anyone faced the same issue already?

Kind regards

Jochen

[Former Member]

Hi Jochen,

Perform a full CPACache refresh with PIDIRUSER. path is http://XIHost:JavaPort/CPACache/refresh?mode=full

if you are still getting the same error then check other wise re create the receiver determination and receiver agreement.

Once you test the ID cofiguration by using the test configuration.

Regards

Ramesh

[Former Member]

Jochen,

Try clearing up the cache. Have you tried sending new messages? I believe this error is coming up only with retrials on the failed messages?

@ Ramesh

if you are still getting the same error then check other wise re create the receiver determination and receiver agreement.

There is no RD / RA / ID / SA when using AAE. That's the advantage of AAE

Regards,

Neetesh

Edited by: Neetesh Raj on Nov 4, 2009 4:30 PM

[Former Member]

Hi guys,

thanks for your answers.

I tried a delta and also a full refres of the CPA Cache.

But restart of the message was not successful. It remain with the same error.

Any other suggestions for this issue

Kind regards

Jochen

[Former Member]

Hi @ll,

issue is still open.

all suggestions doesn´t solve the problem.

obviously no one else has faced the same issue so far.

thanks for your suggestions

Kind regards

Jochen

[Former Member]

HI Jochen,

I feel that you should once go for a CPA Cache refresh from Adapter Engine and try executing your failed messages once again in the adapter engine.

To do a CPA Cache Refresh from the Adapter Engine:

To trigger a cache refresh from the individual Adapter Framework, open a browser window and enter the following URL:

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

The Monitoring url is like this:

http://<host>:<port>/CPACache

Check this How-to Guide on Cache, it will be useful:

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34&override...

Thanks

Dhwani