RESOURCE_NOT_FOUND error

[Former Member]

Hi,

I am working on PI 7.11 (EHP1) version.

we have implemented few soap to proxy interfaces using PI 7.1 EHP1 version.

Intially all interfaces were working fine.Now suddenly all interfaces are getting below mentioned error and once in 10 runs interface is working fine.

RESOURCE_NOT_FOUND</SAP:Code>

<SAP:Stack>Unable to find resource 9e46ea00-f924-11de-8d4e-cb2e0aff1e59 in the following software component versions: http://abc.com/I11_ListCustomVendorscom/sap/xi/tf/_MM_ListCustomVendors_PACReq_to_Lis~-1</SAP:Stack>;

we have done all cache refreshes (CPA Cache..) and cache is up to date.

Donno where it went wrong. Please help us.

Highly appreiciate your help.

Thanks

Hamja

Edited by: Hamja Hussain on Feb 22, 2010 3:55 PM

[former_member200962 · Accepted solution]

Can you tell what is the load on your server (message frequency...high/ low)?

During runtime if there are no adequate resources, then the mapping program does not get loaded and then it may result into the above error......if possible try to restart the server (if the load is low)

[Former Member · Accepted solution]

Hi Abhishek,

Load is reasonalbly low and we already restarted the engine.

Thanks

Hamja

[Former Member · Accepted solution]

Check cache update, The problem exist there only.

[Former Member]

closing the thread since no reply given resolution.

Thanks

Hamja

[Shabarish_Nair]

we are facing a similar issue.

was this resolved for you?

[Former Member]

Hi,

Could anybody please suggest.

Thanks

Hamja

[Former Member]

Hi,

Try this parameter...

Parameter CACHE_DIRTY_READ

Meaning

To speed up the processing of messages, you do not access the data required from the Integration Directory directly, but from a cache. If required, this cache can be refreshed automatically. However, it is still possible that a message is being edited just as the cache is being updated.

If you set the parameter CACHE_DIRTY_READ to 0, no messages are processed while the cache is being refreshed.

If you set the parameter CACHE_DIRTY_READ to 1, message processing is not interrupted by a cache refresh. This is achieved by simply using the status of cache before the cache refresh for the evaluation. Whether this results in outdated data being used depends on whether the messages concerned are in any way connected with the changed data.

Also refer these threads...

Regds,

Pinangshuk.

[Former Member]

Hi,

we have already tried your solution but still issue persists.

Thanks

Hamja