cancel
Showing results for 
Search instead for 
Did you mean: 

SAP PI 7.11 - CPA cache problems

Dimitri
Active Contributor
0 Kudos

Dear,

We noticed 2 different things about the (CPA) cache:

  • When we activate a Data Type and go to Environment in the menu -> Cache Status Overview, nothing is reflected here.
    I expected to see the cache has been updated with Data Type information.
  • Performing a full CPA cache refresh, we get a time out (connection to partner timed out after 600s)

Any help is really appreciated.

Thanks a lot.

Dimitri

Accepted Solutions (1)

Accepted Solutions (1)

Dimitri
Active Contributor
0 Kudos

After some investigation, seems that J2EE_GUEST was locked.

Answers (2)

Answers (2)

hasan_celebi
Participant
0 Kudos

Hi Dimitri;

Can you try following settings;

Go to NWA>Java Properties >Services

Reset XPI Service : CPA Cache (directory password)

Reset XPI Service : All Config Service (service user password)

and check for the directory user and directory password parameters

these parameters do not need to be  changed when changing the PI* user passwords.
they are not used in a central PI system and can be ignored.

Regards
Hasan

Former Member
0 Kudos

Try restarting the server.

Dimitri
Active Contributor
0 Kudos

Already did that and I only see delta cache updates in the history.

That's why I wanted to perform a full cache refresh.

Former Member
0 Kudos

Hi

To avoid cache refresh failed, please follow steps 1, 2, 3, 4, 5 and 6 before performing XI/PI cache refresh manually when necessary.

1. Run "cache connectivity test" via RWB Component Monitoring first

2. Check the setting of the Integration Engine RUNTIME parameter CACHE_DIRTY_READ via transaction SXMB_ADM/SXMB_ADMIN. CACHE_DIRTY_READ=1 is the default and preferred setting.

3. Please consider to increase the value for the following parameters when there are large number of ID objects (for example: more than thousand) needs to be updated to XI/PI runtime caches in order to avoid cache fresh failed due to timeout error or http_communication_failure.

    1. JVM parameter: -Dorg.w3c.www.protocol.http.connections.timeout=600000. This parameter is valid for performing CPA cache refresh via https connection. For detailed information, please refer to note 1365480.
    2. The properties "ServletInputStreamTimeout" and "ServletLongDataTransferTimeout"of J2EE http service via NetWeaver Administration Page (Only valid for XI 3.0 & PI 7.0, but not for PI 7.1). For detailed information, please refer to note 807000.
    3. The timeout option of RFC destination INTEGRATION_DIRECTORY_HMI via transaction SM59

4. For XI/PI Integration Server system or XI/PI non-central adapter engine system consisting of the central and dialog instances, please check the following properties of CPA Cache service com.sap.aii.af.cpa.svc are defined using the hostname and port number of Web dispatcher or hardware load balancer.

    1. SLD.selfregistration.hostName
    2. SLD.selfregistration.httpPort
    3. SLD.selfregistration.httpsPort

5. Check the user who perform cache refresh has enough authorization.

    1. Having role SAP_XI_APPL_SERV_USER and the authorization S_RFC_ADM is contained in this role. For detailed information, please refer to note 1177441.
    2. Having role SAP_XI_ADMINISTRATORABAP and the authorization S_XMB_AUTH is contained in this role, which is required for "Full/Complete Cache Refresh" of PI 7.1.  For detailed information, please refer to note 1122879.

6. Check the following XI/PI system users are not locked via transaction SU01.




You can check more details in the following link


Regards

Osman

Dimitri
Active Contributor
0 Kudos

Hi Osman,

Thank you for the valuable feedback.

This morning, I just tried again and now, this error appears:


Any ideas?

Thanks.

Dimitri