XICACHE COMMUNICATION ERROR

[arunneerolil]

Hi,

In our XI we did some file-to-IDoc and IDoc-to-file scenarios.

Things worked well for a month.

Now all scenarios are showing the same error.

(Monitor for Processed XML Messages)

Error ID -> XICACHE

Error Category -> COMMUNICATION

For Ex: IDoc is coming from R/3 to XI and the processing ends with the above error.

Error File

=========================================================================

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Receiver Identification

-->

- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="XICACHE">COMMUNICATION</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText>if_http_client receive http_communication_failure</SAP:AdditionalText>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>An error occurred when refreshing the XI runtime cache</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

==========================================================================

Can anyone help ?

Thanks in Advance

Chemmam

[Former Member · Accepted solution]

Hi

Check out the HTTP Destination defined in SM59, you might have not mentioned the username and password.

Some time it happens that after filling the password, when you press the other tab button without saving, then the password is lost. So always remember to save the settings as soon as you fill the username and password field.

Regards

Mithlesh

[STALANKI]

You have a guide in service market place.make sure that your cache settings are perfect.

Visit the blogs..for understanding the cache better..:)

/people/sravya.talanki2/blog/2005/12/02/sxicache--ripped-off

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

Iam sure that will be really useful.

[Former Member]

HI Chemmanz

There is some problem in Ur HTTP Destination

Got to sm59.and check HTTP Destination: <b>INTEGRATION_DIRECTORY_HMI</b> settins are okay or not.

Procedure:

1. Log on to your SAP Exchange Infrastructure central instance host.

2. Call transaction SM59.

3. Choose Create.

4. Enter at least the following:

RFC destination: INTEGRATION_DIRECTORY_HMI Connection type: H Description: <your description>

5. Choose ENTER

6. Choose the following tabs and enter the required data:

Tab: Technical Settings

• Target Host: host name of the J2EE engine

• Service No.: HTTP port number (The following naming convention applies: 5<Java_instance_number>00 &#56256;&#56518; 50000, if your Java instance is 00)

• Path Prefix: /dir/CacheRefresh

Tab: Security/Logon

• Select Basic Authentication Confirm both the popup and the warning.

• As logon data enter the client of your SAP XI system and the user XIISUSER with the valid password

Save your entry now, before you switch to next tab, otherwise your entries may be lost.

Press Enter to go to the next screen.

Tab: Special Options

• Timeout: 900

• HTTP Settings: Compression: inactive Compressed Response: No

• HTTP Cookies: Accept Cookies: Yes (All)

7. Choose Test Connection.

The test has been executed successfully if the response status code is 500 and you find REQID not found in the HTTP body.

8. Save your settings.

Cheers,

Vijay Raheja

[arunneerolil]

Hi,

Thanks for all replies.

Rgds

Chemmanz

[Former Member]

Hi Chemmanz,

Please check out the following link on the XI Cache and cache refreshing.

/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions

Hope this helps!!

regards,

Prashanth