We recently patched our DEV system from NW7.02 Supp Pack 10 to NW7.02 Supp Pack 12. Since then we have had problems with the ABAP cache. Not sure whether this is as a result of the patch (i.e. it contained a bug) or there was an issue applying the patch. What is happening is as follows:
* Activate a change to a Configuration Directory object
* View Cache Notifications
* Two lines displayed as follows:
As you can see (if you zoom in on the image) the ABAP Cache has not updated. If you click on the 'Problems' tab there is one associated error which says:
Unable to notify integration runtime (ABAP) of data changes
http connection to "http://devserver/sap/xi/cache?sap-client=001" returns the status code "500" in response
If I go to a browser and enter the URL above I am able to refresh the cache i.e. the cache notifications tab shows 2 green lights. For info I have checked the HMI connection in SM59 and it gives "Internal Server Error 500" which I am led to believe shows it is working.
Any ideas why this patching exercise could have caused this caching issue ?
In our live environment when I activate a change to a configuration directory object the ABAP cache is refreshed immediately. I assume this refresh is triggered by me activating the changed object. Are you saying this is not the case and that there is actually a scheduling element to the ABAP cache refresh ?
every time you activate and object in the Integration Directory will refresh the ABAP Cache. this refreshing is tigth to the RFC destination LCRSAPRFC.
sometimes, for server issues the refresh is not performed once you activated but is rare, in this cases you have the possibility to force it manually as i suggest before.
confirm me a doubt. If you refresh it manually it works?
you have some possilities to check this issue
Check that and let me know
Message was edited by: Rodrigo Alejandro Pertierra
Yes, If I go to a browser and paste in the URL in my first post this refreshes the ABAP cache. My feeling is PI is trying to do the same thing but whatever reason fails...when it didn't used to.
I did the SLDCHECK and it was ok.
What is a CPA Cache ?