on 04-04-2012 10:35 AM
Hi,
Find below details.
CPA Cache Cluster Contents Inconsistent
Context
The essence of the cache update mechanism to keep the central configuration data in sync with the several configuration cache implementations in AS Java and AS ABAP. It is HTTP- based and after any configuration change, the Integration Directory (ID) sends an invalidation event to the CPACache of any known (de)-central Advanced Adapter Engine (AAE).
The AAE then tries to retrieve the changed configuration from the ID, authenticating itself by its SLD instance name. The cache update transports the configuration in XML format. In PCK mode, the CPACache service does not accept any cache invalidation HTTP requests.
Problem
If errors occur in the asynchronous cluster communication, CPA Cache contents of some cluster nodes can become inconsistent.
Probability for such an error is very low, however it cannot be ignored. This issue has also been reported for customer systems. Presently in such case customer needs to restart CPA Cache Service on all cluster nodes, as there is no way to find out the node on which the CPA Cache contents are inconsistent.
Solution
The solution currently available is either to restart the CPA Cache service or to do a full cache refresh. Both solutions are time-consuming for a production system. The new solution is to do the local synchronization. Here the nodes will update their in-memory cache with the CPA objects present in the database.
To trigger a local synchronization, perform the following steps:
1. Open NWA (http://<host>:<port>/nwa) and choose SOA --> Monitoring --> PI Cache Monitoring. Choose Synchronize. This action will trigger the local synchronization of all the nodes. To check the status of synchronization, choose Synchronization Status.
2. Perform a dummy delta refresh using the following link. http://<host>:<port>/ CPACache/refresh?mode=dummy_delta.
Regards,
Venkata S Pagolu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please try SXMB_IFR -> RWB -> Login -> Display -> Cache Connectivity Test and in new page please look out for all green PI components. If its not green, try Cache Connectivity test. Status of all PI component should be green.
Regards
Aashish Sinha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.