"Since CAS holds service registrations in memory, it needs this periodic
flush/reload
to pick up the changes to the database for all nodes other than the
one where changes were made."
I have two clustered tomcat servers (server01, server02), each with a
CAS instance. What do I have to do to replicate the Database to be
consistent in both servers? I have this periodic flush/reload configured
in both servers..
Francisco
Marvin Addison wrote:
Im a little bit confused by this. I have one tomcat server with one entry
(service) in the DB.
If you have only one CAS instance, clustering doesn't apply and you
can ignore that section.
By adding those lines in *ticketRegistry.xml, *it
should replicate this entry to the other tomcat server in the cluster? Or
everytime I add a service it replicates to the other server in the cluster?
It doesn't cause replication. It's simply a periodic trigger to
reload the registered services from the database. In a clustered
scenario, when you add/modify/delete a service, the update only
applies to the node on which you made the change. Since CAS holds
service registrations in memory, it needs this periodic flush/reload
to pick up the changes to the database for all nodes other than the
one where changes were made.
M
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
