>> Failed: ticket 'ST-2-3VLTJeYvjeAfx5NutNPO-cas' not recognized". No errors >> show in the logs.
This means the ticket cannot be found in the ticket registry. No error is logged, but an INFO message like the following is logged: 2010-06-01 12:00:00 org.jasig.cas.CentralAuthenticationServiceImpl INFO ServiceTicket [ST-2-3VLTJeYvjeAfx5NutNPO-cas] does not exist. > - Attempting to fully cluster the CAS server as described in the “Clustering > CAS” tutorial (http://www.ja-sig.org/wiki/display/CASUM/Clustering+CAS) > fails. Reason: jBoss 5 changed jBossCache, making the > jbossTicketCacheReplicationConfig.xml from the CAS 3.3.1 distribution > (jbossTestCache.xml) and possibly some of the other configuration > instructions no longer work. I am trying to reconfigure for jBoss 5 but > honestly I don’t understand jBossCache nor CAS’ internal behavior well > enough. I'm only aware of one active member of the CAS community who is very knowledgeable about JBoss Cache and may be able to help you. Hopefully Mihir will speak up. I suspect that your HA singleton setup may not be configured correctly. For example if you do not have JBoss Cache working properly, then ticket state data is not replicated to the hot standby. Additionally, if the validation request somehow gets to the standby instead of the primary, then obviously the ticket would not be in the registry. Once you get your distributed ticket registry set up correctly, it will be a non-issue since JBoss Cache will take care of ticket state replication to the standby. But it should be of concern to you that requests are presumably being sent to the standby. 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
