Anyone?
On 10/1/08 2:17 PM, "Andrew Feller" <[EMAIL PROTECTED]> wrote: > Since we originally deployed CAS, a sample configuration file for Jboss Cache > has been distributed with the CAS server ( > https://www.ja-sig.org/svn/cas3/tags/cas-3-2-1-final/cas-server-integration-jb > oss/src/test/resources/jbossTestCache.xml ). Upon comparing it with our > current configuration, I have noticed there have been several discrepancies, > which I hoped could be explained. > > JGroups discrepancies > 1. <FD> has been commented out in favor of <FD_SOCK> > 2. <pbcast.NAKACK> and <UNICAST> are both used > 3. <FRAG> has been included > > JBoss Cache Discrepancies > 1. UseReplQueue, ReplQueueInterval, ReplQueueMaxElements are declared but are > only used by asynchronous replication > 2. TransactionManager is specified yet the online documentation for cluster > has it being removed ( http://www.ja-sig.org/wiki/display/CASUM/Clustering+CAS > ) > > My primary focus is on the JGroup changes as I don¹t know if FD_SOCK uses the > same notion of shunning as FD. The source behind FD_SOCK shows removal of > suspect members and broadcasting the removal to the cluster, so it should be > okay. I am also curious why the <FRAG> entity was introduced; were people > having replication packets that were too large or being blocked due to size? > > Thanks, > Andrew -- Andrew R. Feller, Analyst Information Technology Services 200 Fred Frey Building Louisiana State University 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
