By default, each EventServer listens on a randomly assigned available port chosen by the operating system. If you prefer, you can configure each EventServer component to have an assigned port so that port numbers are consistent from one run to the next. To do this, you set the port property of the EventServer component.
You can also configure a SQL repository so that it does not automatically update the das_gsa_subscriber table. Do this by setting the autoUpdateSubscribers property of the GSARepository component to false. With this setting, ATG will not add or remove items from the das_gsa_subscriber table. A server will print a warning if it is unable to find itself in the table when it tries to send an invalidation event. A server also prints a warning if it is unable to send an event to one of the servers listed in the table. If you are able to modify items with cache-mode="distributed" on each server without seeing any warnings, your das_gsa_subscriber table is configured correctly.
If you want to disable the autoUpdateSubscribers mode, you can still use it to populate the default contents of the das_gsa_subscriber table. To do this, you will need to assign available ports for the SQLRepositoryEventServer component on each server in your cluster. Initially, leave the autoUpdateSubscribers property of the GSARepository components set to its default value (true) and start all servers in your cluster. Once all servers have started up, the contents of this table should be populated with unique available port numbers. Now stop all servers, using <ctrl-C> (to prevent them from removing themselves on exit) and then set autoUpdateSubscribers=false for each GSARepository component that uses distributed cache mode. When you start the servers in the cluster this time, they will neither add nor remove themselves from the table.
