cancel
Showing results for 
Search instead for 
Did you mean: 

Cache refresh error, while activating changelists

Former Member
0 Kudos

Hi all,

I got a problem, concerning XI Runtime Cache on XI 3.0, SP15 -> when I try to activate changelists from Integration Directory, (SOMETIMES!)XI_CACHE shows status: Error, while refreshing cache

with Errortype: Communication,

"if_http_client receive http_communication_failure"

When I then do a delta or full cache refresh from transaction SXI_CACHE it allways works, even after an error occured before. Some ideas, what I could check?

Thank you in advance..

Daniel

Accepted Solutions (1)

Accepted Solutions (1)

moorthy
Active Contributor
0 Kudos

Hi,

Just check with Tcode SICF and check for all the services are working fine.

Go thru following links

http://service.sap.com/NW04 ->How-to Guides-> Exchange Infrastructure->How To handle Caches in SAP XI 3.0

Also go thru following thread.

Hope this helps.

Regards,

Moorthy

Regards

Suraj

Regards,

Moorthy

Answers (3)

Answers (3)

Former Member
0 Kudos

I try to explain it once again,

the Cache Refresh from SXI_CACHE to Integration Directory works allways, doing it in transaction...

BUT...if I try to activate my changelist from Integration Directory and check then the cache status in TA SXI_CACHE I got communication errors. The weird thing is, that happens not allways, only in 50 % of the cases.

In my understanding that means the mechanism works in general, but sometimes it fails (even when activating the same objects from Integration Directory)

Does ID really uses the HTTP RFC Destination: INTEGRATION_DIRECTORY_HMI to update the IS Cache? (I am not sure)

If not, how is the communication in that direction then established? I checked the Exchange Profile Parameters on J2EE-Side, they are correct... like I said... sometimes it works (make me think, at least the authentication data and the connection parameter must be correct, right?)

I have no idea...

Daniel

Shabarish_Nair
Active Contributor
0 Kudos

We had some wierd issues with cache. But finally the only solution that we found was to schedule the report SAI_CACHE_REFRESH in the background so that the cache is forced to refresh.

Maybe if you are still stuck without a solution, try this out !!!

~ShaBZ~

Former Member
0 Kudos

Hi Daniel,

We end up in cache refresh error though the configurations are correct due to the inconsistent objects either in IR or ID.

For Ex: ID is referring to a mapping object in the IR, which is no longer present. This might happen very frequently when migrating several objects from development to QA if proper care has not been take to address that.

Please go thru this link which will help you understand your problem and also to find a solution to it:

/people/sravya.talanki2/blog/2005/11/03/cache-refresh-errors--new-phenomena

Hope this helps you solve your problem.

Regards,

abhy

PS: AWARD POINTS FOR HELPFUL ANSWERS.

Former Member
0 Kudos

Thanks for approach,

but that won't solve my problem, to check SICF just makes clear, that the SAP Service is doing fine, something I allready know, necause using transaction SXI_CACHE uses that services and works allways.

I guess, my problem is the opposite direction, i.e. the Integration Directory trying to send activated changelists to IS, that sometimes fails with a communication error, as described above.

Please help me out!

moorthy
Active Contributor
0 Kudos

Hi Daniel,

Check with Cache Monitoring of RWB. It may help you finding out the problems.

It happend once for me. Then I tried with restarting the J2EE Service and it get resolved. But usually it gets resolved in Delta Cache/RWB cache refresh..

May be helpful..

Regards,

Moorthy

Former Member
0 Kudos

hi Check the exact name of the connection

INTEGRATION_DIRECTORY_HMIin Transaction sm59. Double check it. Sometimes if you misspell it, like i.e

INTREGATION_DIRECTORY_HMI, this happens. Additionally check the in the log on tab that Basic authentification is set and not SAP Standard.

Regards,

Jaime