Scott,
I'm really happy to ear that Rutgers is taking this step forward !
You will found in copy the configuration we used with Marc-Antoine during
our stress test compaign in Fall 2006. I guess this is also the current
production configuration, but I won't be able to confirm it (not anymore
working for this customer).
By the way, we were not JGroups experts. But stress tests were OK in our
context. Feedback welcome, just in case if I might be able to push another
cas cluster into production in the future ;-)
Regards,
-Arnaud
On Feb 4, 2008 9:26 PM, Scott Battaglia <[EMAIL PROTECTED]> wrote:
> All,
>
> We're currently looking at deploying a JBossCached backed TicketRegistry
> here at Rutgers. Unfortunately, none of us are JGroups experts here. If
> anyone can send me a copy of their TCP configuration (minus any confidential
> information) that would be highly appreciated. If anyone has any
> tips/hints/gotchas about using JGroups, please feel free to send them to the
> list so we can all benefit :-)
>
> Thanks
> -Scott
> --
> -Scott Battaglia
> LinkedIn: http://www.linkedin.com/in/scottbattaglia
> _______________________________________________
> cas-dev mailing list
> [email protected]
> http://tp.its.yale.edu/mailman/listinfo/cas-dev
>
>
--
Arnaud Lesueur
LinkedIn: http://www.linkedin.com/in/lesueur
<?xml version="1.0" encoding="UTF-8"?>
<!-- ===================================================================== -->
<!-- -->
<!-- Sample TreeCache Service Configuration -->
<!-- -->
<!-- ===================================================================== -->
<server>
<!-- ==================================================================== -->
<!-- Defines TreeCache configuration -->
<!-- ==================================================================== -->
<mbean code="org.jboss.cache.TreeCache"
name="jboss.cache:service=TreeCache">
<!--
Configure the TransactionManager
<attribute name="TransactionManagerLookupClass">org.jboss.cache.DummyTransactionManagerLookup</attribute>
-->
<!--
Isolation level : SERIALIZABLE
REPEATABLE_READ (default)
READ_COMMITTED
READ_UNCOMMITTED
NONE
-->
<attribute name="IsolationLevel">NONE</attribute>
<!--
Valid modes are LOCAL
REPL_ASYNC
REPL_SYNC
INVALIDATION_ASYNC
INVALIDATION_SYNC
-->
<attribute name="CacheMode">REPL_SYNC</attribute>
<!--
Just used for async repl: use a replication queue
-->
<attribute name="UseReplQueue">false</attribute>
<!--
Replication interval for replication queue (in ms)
-->
<attribute name="ReplQueueInterval">0</attribute>
<!--
Max number of elements which trigger replication
-->
<attribute name="ReplQueueMaxElements">0</attribute>
<!-- Name of cluster. Needs to be the same for all clusters, in order
to find each other
-->
<attribute name="ClusterName">CAS</attribute>
<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml
<attribute name="ClusterProperties"></attribute>
-->
<attribute name="ClusterConfig">
<config>
<TCP bind_addr="10.155.18.126" start_port="7800" loopback="true"/>
<TCPPING initial_hosts="10.155.16.132[7800]"
port_range="3"
timeout="3500"
num_initial_members="3"
up_thread="true"
down_thread="true"/>
<MERGE2 min_interval="5000" max_interval="10000"/>
<FD shun="true" timeout="2500" max_tries="5" up_thread="true" down_thread="true" />
<VERIFY_SUSPECT timeout="1500" down_thread="false" up_thread="false" />
<pbcast.NAKACK down_thread="true" up_thread="true" gc_lag="100" retransmit_timeout="300,600,1200,2400,4800,9600" />
<pbcast.STABLE desired_avg_gossip="20000" down_thread="false" up_thread="false" stability_delay="1500"/>
<pbcast.GMS join_timeout="5000"
join_retry_timeout="2000"
shun="true"
print_local_addr="true"
down_thread="true"
up_thread="true"/>
<pbcast.STATE_TRANSFER up_thread="true" down_thread="true" />
</config>
</attribute>
<!--
Whether or not to fetch state on joining a cluster
NOTE this used to be called FetchStateOnStartup and has been renamed to be more descriptive.
-->
<attribute name="FetchInMemoryState">true</attribute>
<!--
The max amount of time (in milliseconds) we wait until the
initial state (ie. the contents of the cache) are retrieved from
existing members in a clustered environment
-->
<attribute name="InitialStateRetrievalTimeout">120000</attribute>
<!--
Number of milliseconds to wait until all responses for a
synchronous call have been received.
-->
<attribute name="SyncReplTimeout">15000</attribute>
<!-- Max number of milliseconds to wait for a lock acquisition -->
<attribute name="LockAcquisitionTimeout">10000</attribute>
<!--
Indicate whether to use marshalling or not. Set this to true if you are running under a scoped
class loader, e.g., inside an application server. Default is "false".
-->
<attribute name="UseMarshalling">true</attribute>
<attribute name="StateTransferVersion">140</attribute>
<!--attribute name="CacheLoaderConfiguration">
<config>
<passivation>false</passivation>
<preload>/</preload>
<shared>false</shared>
<cacheloader>
<class>org.jboss.cache.loader.ClusteredCacheLoader</class>
<properties>
timeout=1000
</properties>
<async>false</async>
<fetchPersistentState>false</fetchPersistentState>
<ignoreModifications>false</ignoreModifications>
</cacheloader>
</config>
</attribute-->
</mbean>
</server>
_______________________________________________
cas-dev mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas-dev
