> out 2 clustered Tomcats each with its own CAS working as cluster (tomcat > session-replication via TCP and JBOSS-TreeCache for tickets) are usualy > rebooted nightly with a gap of one hour.
I'm curious why you do a nightly restart. While some truly misbehaving applications need this, it's very uncommon for such drastic measures to be required for CAS. I've never heard of it in my many years in the CAS community. > Do you have an idea what the cause might be? No idea, but from the stack trace it looks like a TreeCache issue that is bubbling up to CAS. > Caused by: org.jgroups.StateTransferException: 1.8.6.35:58525 could not fetch > state null from null > at org.jgroups.JChannel.connect(JChannel.java:466) > at org.jboss.cache.RPCManagerImpl.start(RPCManagerImpl.java:147) > ... 64 more > Caused by: org.jgroups.StateTransferException: 1.8.6.35:58525 could not fetch > state null from null > at org.jgroups.JChannel.connect(JChannel.java:459) > ... 65 more This smells like a networking problem. I'm only vaguely familiar with TreeCache and JGroups, but it's my experience that many if not most cache issues are due to replication and state transfer failures. That looks to be the case here. I'm curious what replication method you're using; TCP or UDP multicast. In any case you should probably concentrate on replication and possibly do some network traffic capture and analysis, and possibly post to the jgroups forum as a follow up. 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
