Over a year ago, Arnaud Lesuer was good enough to post a TCP-based JBoss configuration for the JBoss integration portion of CAS. While doing our internal stress tests, I compared the configurations and noticed there were a handful of discrepancies. Can anyone provide commentary whether the older TCP configuration is still valid? Is there an updated configuration for TCP?
Discrepancies: 1. CAS 3.0.X TCPPING has both up_thread and down_thread set to true while CAS 3.2 PING has both up_thread and down_thread as false 2. CAS 3.0.X has FD entry while CAS 3.2 has FD_SOCK entry with no attributes 3. CAS 3.0.X pbcast.NAKACK has up_thread and down_thread set to true while CAS 3.2 has both set to false 4. CAS 3.0.X has pbcast.GMS specifying both up_thread and down_thread set to true while CAS 3.2 doesn't have either set CAS 3.2 Final JBoss configuration: https://www.ja-sig.org/svn/cas3/tags/cas-3-2-0-final/cas-server-integrat ion-jboss/src/test/resources/jbossTestCache.xml CAS 3.0.X JBoss TCP configuration: http://www.nabble.com/Re%3A-Cluster-with-JBossCacheTicketRegistry-p10379 079.html Thanks! Andy Andrew R Feller, Analyst University Information Systems 200 Fred Frey Building Louisiana State University <http://www.lsu.edu/> Baton Rouge, LA, 70803 (225) 578-3737 (Office) (225) 578-6400 (Fax)
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
