Jboss Session Replication Problem on Linux.

[svelur]

I set up two servers for session replication.
The servers run fine for some time. When 5 users simultaneously start testing, it failed with following error:

Any help is greatly appreciated.


---------
2005-08-03 20:23:55,994 9882568 WARN [org.jboss.cache.interceptors.ReplicationInterceptor] (http-0.0.0.0-8080-7:) runPreparePhase() failed. Transaction is marked as rolled back
org.jboss.cache.lock.TimeoutException: rsp=sender=10.38.9.176:33001, retval=null, received=false, suspected=false
at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:2186)
at org.jboss.cache.TreeCache.callRemoteMethods(TreeCache.java:2208)
at org.jboss.cache.interceptors.ReplicationInterceptor.runPreparePhase(ReplicationInterceptor.java:485)
at org.jboss.cache.interceptors.ReplicationInterceptor$SynchronizationHandler.beforeCompletion(ReplicationInterceptor.java:389)
at org.jboss.cache.interceptors.OrderedSynchronizationHandler.beforeCompletion(OrderedSynchronizationHandler.java:77)
at org.jboss.tm.TransactionImpl.doBeforeCompletion(TransactionImpl.java:1384)
at org.jboss.tm.TransactionImpl.beforePrepare(TransactionImpl.java:1076)
at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:296)
at org.jboss.tm.TxManager.commit(TxManager.java:200)
at org.jboss.web.tomcat.tc5.session.JBossCacheManager.endTransaction(JBossCacheManager.java:505)

[ben.wang]

you will need to describe your enviornment in more detailed, AS version, what kind of testing, etc.

-Ben

[svelur]

We are using JBoss 4.0.2

Here is my config files for clustering:

tc5-cluster-service.xml:
---------------------------



jboss:service=Naming
jboss:service=TransactionManager

<!-- Configure the TransactionManager -->
org.jboss.cache.JBossTransactionManagerLookup

<!--
Isolation level : SERIALIZABLE
REPEATABLE_READ (default)
READ_COMMITTED
READ_UNCOMMITTED
NONE
-->
REPEATABLE_READ

<!--
Valid modes are LOCAL, REPL_ASYNC and REPL_SYNC
-->
REPL_SYNC

<!-- Name of cluster. Needs to be the same for all clusters, in order
to find each other
-->
Tomcat-Cluster

<!-- JGroups protocol stack properties. Can also be a URL,
e.g. file:/home/bela/default.xml

-->


<!--
The default UDP stack:
- If you have a multihomed machine, set the UDP protocol's bind_addr attribute to the
appropriate NIC IP address, e.g bind_addr="192.168.0.2".
- On Windows machines, because of the media sense feature being broken with multicast
(even after disabling media sense) set the UDP protocol's loopback attribute to true
-->


<UDP bind_addr="10.38.9.174" mcast_port="45577"
ip_ttl="8" ip_mcast="true"
mcast_send_buf_size="150000" mcast_recv_buf_size="80000"
ucast_send_buf_size="150000" ucast_recv_buf_size="80000"
loopback="true"/>
<PING timeout="2000" num_initial_members="3"
up_thread="false" down_thread="false"/>
<MERGE2 min_interval="10000" max_interval="20000"/>

------------------
jboss-service.xml
-------------------
<!--
Configuration for HTTP Session Clustering using JBossCache
-->
jboss.cache:service=TomcatClusteringCache
jboss:service=TransactionManager

----------------------
web.xml
-----------------------
<web-app>


<servlet-name>jsp</servlet-name>
<servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class>
<init-param>
<param-name>fork</param-name>
<param-value>false</param-value>
</init-param>

--------------------------
jboss-web.xml
--------------------------
<replication-config>
<replication-trigger>SET_AND_NON_PRIMITIVE_GET</replication-trigger>
<replication-granularity>SESSION</replication-granularity>
</replication-config>






-----------------------------------------------------------------------------------
-----------------------------------------------------------------------------------

After I received lock and timeout exception ,
I set up ISOLATION to "NONE"
and CachMode to "REPL_ASYNC"

even with this, it is tremendously slow. Any idea??