SAP PI Cache Problem

[Former Member]

Dear all,

I am developing different scenarios with BPMs accessed by SOAP (Web Services) within SAP-PI.

I am having a lot of problems with some of the XSLT split mappings programs. What's happening is that we have developed various mappings and made changes to them and upon activating them it's possible that they are being incorrectly managed by the J2EE server cache e.g. wrong versions being kept in the cache. The consequence of this is that we obtain different results for the same data input.

Executing the services sequentially, with the same input parameters, we obtain results with different data in a random form that coincides with the different versions of the mappings that we have published to the server.

Could there be an error with the way the java cache works?

I am checking different issues regarding the SAP PI Caché manual ("How to Handle Caches in SAP XI 3.0.pdf"), but I cannot find the problem. Doing testing, I am getting in different moments, following errors:

1. This error occurs sometimes:

com.sap.aii.af.service.cpa.impl.exception.CPADirectoryCacheException: Failed to check secure connection configuration. Reason: com.sap.aii.af.lib.sld.SLDException: Failed to read SLD instance name. Reason: HTTP response code: 503 (Service Unavailable)

at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDirectoryURL(DirectoryAccess.java:134)

at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDeltaRefreshURL(DirectoryAccess.java:191)

at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryAccess.getDeltaCacheUpdateXML(DirectoryAccess.java:440)

at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:491)

at com.sap.aii.af.service.cpa.impl.cache.CacheManager$CacheUpdateRunnable.run(CacheManager.java:322)

at com.sap.engine.frame.core.thread.Task.run(Task.java:73)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:144)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:242)

Caused by: com.sap.aii.af.lib.sld.SLDException: Failed to read SLD instance name. Reason: HTTP response code: 503 (Service Unavailable)

I did all checks that came in the manual, but to no avail.

Thanks in advance.

Regards

[Shabarish_Nair]

what does SXI_CACHE show?

Usually the resource not found error has been seen to disappear on restarting the java stack. Can you try that too?

[Former Member]

This "ramdom" errors could be due to amount of maximum java memory heap of the different J2ee servers?