You can configure an SQL repository so it does not automatically update the das_gsa_subscriber table, by setting the SQL Repository component’s autoUpdateSubscribers property to false. In general, you do this in order to protect a live site from updates that are liable to degrade performance.
When updates to das_gsa_subscriber are disabled, ATG does not add or remove items from the das_gsa_subscriber table. In this case, it only prints warnings when an event server:
Tries to send a cache invalidation event and cannot find itself in the table.
Cannot send a cache invalidation event to a server that is listed in the table.
You can confirm that cache invalidation events are distributed correctly if you can modify items that use distributed TCP caching on each server and avoid any warnings.
Populating das_gsa_subscriber
A site that prohibits updates to das_gsa_subscriber assumes that the table is fully populated with valid caching data. However, this table can only be populated if updates are initially enabled. In order to circumvent this problem, follow these steps:
On each participating ATG instance, set the event server component’s
portproperty to an available port.For each repository that uses distributed TCP caching mode, make sure that its SQL Repository component’s
autoUpdateSubscriberproperty is set to true (the default).Start all ATG instances in the cluster.
After all ATG instances start, the contents of
das_gsa_subscribershould be populated with unique port numbers.Dump the contents of
das_gsa_subscriberto a backup file, so the data can be restored later.Stop all ATG instances that participate in distributed TCP caching.
For each repository that uses distributed TCP caching mode, reset its SQL Repository component’s
autoUpdateSubscriberproperty to false.Insert the dumped output into
das_gsa_subscriber.Restart the ATG instances.
