CAS cluster don"t replicate tickets

[user []

 configure a clustered CAS 3.0.7 platform, following the instructions at  > /login <  http://itforwallstreet.com/wiki/display/CASUM/Clustering+CAS#ClusteringCAS-r  http://itforwallstreet.com/tp/cas'  [mailto:  http://itforwallstreet.com/mailman  ] On Behalf Of Claudio Tassini Sent: Tuesday, August 21, 2007 8:17 AM To: Yale CAS mailing list Subject: Re: CAS cluster don't replicate tickets     2007/8/21, Andrew R Feller <  afelle1 at lsu.edu  visible is both that both Tomcat clustering and CAS clustering are configured correctly?  By using Tomcat 5.5, I assume to do this to it's clustering works because I can see that you are using multicasting for both Tomcat and CAS; only Tomcat 6.0 supports unicast discovery via static members.     I'm not really expert about step-by-step way? ;P      Furthermore, we're using Jboss Cache 1.4.1SP4, Tomcat 5.5 and CAS 3.0.7 with JDK 1.6. Should these versions be compatble with each other?        Hope that Tomcat clustering works.  As for CAS, I think you should be able to log at the org.jasig.cas.ticket.registry package to monitor the JBoss Cache ticket registry.  jboss cache 2.0   tomcat 5.5   cas 3.0.7      I'm sorry but as I said before I'm not really expert about tomcat , but I can say that logging level to debug for the servers using the tomcat. Could you explain how to me in a >:  Are you sure that helps,     Andrew R Feller, Analyst  Subversion Administrator  University Information Systems  Louisiana State University a test jsp.   [Andrew R Feller]      Try changing the org.apache.catalina.cluster package by confirm that each established connection generates a sessionID wich  Messages sorted by:  (office) 225.578.3737   ________________________________   From:  http://itforwallstreet.com/application  [mailto:  CAS cluster don"t replicate tickets  (office) 225.578.3737  ________________________________  From:  >  /proxyValidate <  Andrew R Feller, Analyst  Subversion Administrator  University Information Systems  Louisiana State University  ] On Behalf Of Claudio Tassini Sent: Tuesday, August 21, 2007 7:10 AM To:  <mailto:  http://itforwallstreet.com/wiki/display/CASUM/Clustering+CAS#ClusteringCAS-re  the same tomcat a single-server environment, but after having configured cas and tomcat to user by the webapp are on the cas login url. Once the application for validation:      Aug 21, 2007 2:02:29 PM edu.yale.its.tp.cas.client.CASReceipt getReceipt  SEVERE: validation of [[edu.yale.its.tp.cas.client.ProxyTicketValidator proxyList=[null] [edu.yale.its.tp.cas.client.ServiceTicketValidator casValidateUrl=[  > /Application <  afelle1 at lsu.edu for Messages sorted by:  http://itforwallstreet.com/Application  redirect to browser to  http://itforwallstreet.com/application  <  http://itforwallstreet.com/application  /application <  https://itforwallstreet.com/cas  http://itforwallstreet.com/pipermail/cas/attachments/20070821/f56b7b08/attachment.html the browser back to  c.tassini at domain.it  <  cas-bounces at itforwallstreet.com  > /application <  CAS cluster don't replicate tickets  following credentials:  http://itforwallstreet.com  >      --  Claudio Tassini   -------------- next part -------------- An HTML attachment was scrubbed... URL: to >  2007-08-21 11:52:07,949 INFO [org.jasig.cas.CentralAuthenticationServiceImpl ] - <Granted service ticket [ST-3-tqk4bNPe05dvGmgaeJCkBidNCEvNOndyekq-server2] for service [  > /listinfo/cas <  <  CAS cluster don"t replicate tickets  cas at itforwallstreet.com  CAS cluster don"t replicate tickets  afelle1 at lsu.edu  cas at itforwallstreet.com  [ author ]  Tue Aug 21 09:35:17 EDT 2007  eferences>   .     We connect to replicate sessions and tickets among two server, we have this behavior:     The user goes to  https://itforwallstreet.com/cas  <  cas mailing list  c.tassini at domain.it  http://itforwallstreet.com/mailman/listinfo/cas  > ] ticket=[ST-3-tqk4bNPe05dvGmgaeJCkBidNCEvNOndyekq-server2] service=[http%3A%2F%2Fitforwallstreet.com%3A8080%2FApplication] errorCode=[INVALID_TICKET] errorMessage=[ticket 'ST-3-tqk4bNPe05dvGmgaeJCkBidNCEvNOndyekq-server2' not recognized] renew=false entireResponse=[<cas:serviceResponse xmlns:cas=' ( > ]>        And this is working flawlessly with a webapp which redirects to the login is from the 5.5).  All is done, cas redirects the webapp page. cas and to the other server, contacted  https://itforwallstreet.com/cas/login  >           <cas:authenticationFailure code='INVALID_TICKET'>                  ticket 'ST-3-tqk4bNPe05dvGmgaeJCkBidNCEvNOndyekq-server2' not recognized           </cas:authenticationFailure>  </cas:serviceResponse>  ]]]] was not successful.       Any idea the remote server. Shouldn't they be syncronized? What could be wrong?   With the ticket:      2007-08-21 11:52:07,947 INFO [org.jasig.cas.authentication.AuthenticationManagerImpl] - <AuthenticationHandler: org.jasig.cas.adaptors.ldap.BindLdapAuthenticationHandler successfully authenticated the two servers, all works fine.     This is an extract from the given ticket is not valid because obtained from the server that grants the same configuration, and shutting down one of the user which provided the log, on the what could be wrong?      Thanks in advance.      --  Claudio Tassini    _______________________________________________ Yale CAS mailing list about >  , which find that  http://itforwallstreet.com  
	 cas-bounces at itforwallstreet.com  <  https://itforwallstreet.com/cas/proxyValidate  c.tassini at domain.it  http://itforwallstreet.com/mailman/listinfo/cas  Subject: CAS cluster don't replicate tickets     Hi all,     we're trying  >  . The application doesn't find a suitable ticket, so redirects the >  . The user logs in successfully and cas tries