When you use the TCP-based distributed cache mode, it is possible for a server to occasionally miss cache invalidation events. This can happen if the server temporarily fails to connect to another server. If a server does fail to connect, there are various safeguards in place so that it receives the event once the connection is re-established. However, even with these safeguards, there can sometimes be missed events.
To ensure that invalidation events are not missed, you can instead use cache-mode=“distributedJMS”. This mode ensures that servers always receive the cache invalidation events, but it should be used only for items that are updated infrequently, because performance is considerably slower than for distributed mode.
When cache-mode=“distributedJMS”, communication of invalidation events is done using JMS. Each Repository component refers to a GSAInvalidatorService component that is configured as a message source in Patch Bay. When a repository item is updated, the GSAInvalidatorService component sends a JMS message for this event. A GSAInvalidationReceiver component is configured as a message sink in Patch Bay, and is a durable subscriber to the topic that receives these messages.
To use cache-mode=“distributedJMS”, you must enable the GSA Cache Invalidator on all servers, and make sure that this service is configured properly. See Cache Invalidation Service for more information.
