tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From michelle wang <cnwan...@gmail.com>
Subject Why only one Web APP can be clustered?!
Date Mon, 31 Oct 2005 19:32:36 GMT
I have been fighting with this for a while, still have no clue at all. Any
help is appreciated!!
 we are running 2 tomcat instances (5.0.18) on one Solaris 9 box with
SimpleTcpClustering. There are 4 applications needs to be clustered.
However, there's only one application can transfer the session status over
the cluster, in fact, it's always the first webapp ( in alphabet order) that
can be clustered. For example, the 4 app's name are "comqa", "comstg",
"hqqa", "hqstg", it's always "comqa" that successfully passes the session
info. But if I rename "comstg" to "aaa" it becomes the one works fine while
comqa stop working any more.
 For each application, I have tested leaving it as the only WEB APP in the
cluster ( remove the rest app_name.xml under tomcat/conf/Catalina/localhost,
and remove the rest app_name directories from tomcat/webapps) each one works
fine for session replication individually. But as long as I put the rest
back, again there's only "comqa" works.
 Is there any setting restricts the clusterable applications to be one only?
Where is it?
 Every web application has < distributable /> in its web.xml. Here's the
server.xml of the cluster:
<Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
name="FilipsCluster"
debug="10"
serviceclass="org.apache.catalina.cluster.mcast.McastService"
mcastAddr="228.0.0.8 <http://228.0.0.8>" ## same mcastAddr on the other
tomcat instance
mcastPort="45565" ## same mcastPort on the other tomcat instance
mcastFrequency="500"
mcastDropTime="3000"
tcpThreadCount="15"
tcpListenAddress="auto"
tcpListenPort="4001" ## tcpListenPort is "4002" on the other tomcat instance
tcpSelectorTimeout="100"
printToScreen="false"
expireSessionsOnShutdown="false"
useDirtyFlag="true"
replicationMode="pooled"
/>
  Here's the error message shown in catalina.out when starting tomcat
showing the application's session state didn't transfered.
WARNING: Manager[/comstg], requesting session state from
org.apache.catalina.cluster.mcast.McastMember[
tcp://206.47.63.195:4002,206.47.63.195,
4002, alive=96819]. This operation will timeout if no session state has been
received within 60 seconds
Oct 25, 2005 10:41:53 AM org.apache.catalina.cluster.session.DeltaManagerstart
SEVERE: Manager[/comstg], No session state received, timing out.
 Thanks!

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message