Johan, Yes, you can increase the verbosity of logging statements through Log4J. Go into /WEB-INF/classes/log4j.properties and create something to the effect of:
log4j.logger.org.jboss.cache = TRACE log4j.logger.org.jgroups = TRACE You should be careful though as this could cause your logs to grow pretty large. On a different note thought, we currently use the JBoss Cache approach and are not satisfied with it in terms of replication stability. There have been several people on the list off and on over the past 2 years that have tried but haven¹t had much luck either. If you are just starting out, I recommend going the Memcached approach if all you need is 2 CAS servers replicating with one another. HTH, A- On 3/24/09 2:28 PM, "Johan Reinalda" <[email protected]> wrote: > All, > > I have just gotten a test environment configured with the cluster-config as > described in the wiki (ie tomcat session replication and ticket replication > via the jbossTicketCacheReplication. > > I can see tomcat session replication working via the manager app. > > On both servers I can see the JBoss startup messages (GMS...), but how to I > verify that ticket replication is actually happening (short of testing the > failover). Is there a way to turn on addtional logging messages to see tickets > being replicated ? > > As always, thanks! > > Johan > PS environment is RHEL5.2, Tomcat6.0.18, CAS3.3.2-snapshot > -- Andrew Feller, Analyst LSU University Information Services 200 Frey Computing Services Center Baton Rouge, LA 70803 Office: 225.578.3737 Fax: 225.578.6400 -- 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
