Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of cnwangli@gmail.com designates
 72.14.204.204 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=aI9vWKAcYJgJ12x1lzyZoetMB60WhShKItWh8qjuD304MRKVGkKC6X9fDpSP7CJwQBxPHqbPpm/N0Wq+n72tsol3/ArCJgyFkxXJRif4/CQQ+dnjY17CM2L9J+r8zPRZPQ7CJeh7R9XZ1cfrwZwVIK3X4dv2qjDpKGvL3E55qus=
Message-ID: <a2533f1c0510251015p390a5b3n8c5470de31090b41@mail.gmail.com>
Date: Tue, 25 Oct 2005 13:15:06 -0400
From: michelle wang <cnwangli@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org>
Subject: Again Please Help!!! SimpleTCPCluster,
 No session state received time out 60s during start up
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_6239_5445175.1130260506254"

------=_Part_6239_5445175.1130260506254
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

---------- Forwarded message ----------
From: michelle wang <cnwangli@gmail.com>
Date: Oct 24, 2005 8:49 PM
Subject: Please Help!!! No session state received, time out 60s during
tomcat start up
To: users@tomcat.apache.org

I'm running 2 tomcat (5.0.18) instances with Simple TCP Clustering on the
same Solaris 9 server, there are multiple web applications need to be
clustered. When starting up the secondary tomcat, there is only one webapp
receives the session state while all others wait 60 seconds and time out.
The strange thing is which web app can successfully receive the session
state seems to be random, I have seen different web app reports receiving
session state, but never more than one of them at one time . Once tomcat is
started, the session replication just works fine even for those application
reports time out during startup. I can always kill the tomcat which is
serving the user session, the other tomcat takes control without losing any
user input. It's very annoying that because each instance time out 60s the
secondary tomcat always takes a few minutes to start up. I have been lookin=
g
into this for a whole week without any clue :( Any help is appreciated
 All web app needs to be clustered has <distributable /> in their web.xml
Here's the cluster configuration in server.xml

<Cluster className=3D"org.apache.catalina.cluster.tcp.SimpleTcpCluster"
name=3D"FilipsCluster"
debug=3D"10"
serviceclass=3D" org.apache.catalina.cluster.mcast.McastService"
mcastAddr=3D"228.0.0.8 <http://228.0.0.8/>" ##same mcastAddr on the other
tomcat
mcastPort=3D"45565" ##same mcastPort on the other tomcat
mcastFrequency=3D"500"
mcastDropTime=3D"3000"
tcpThreadCount=3D"6"
tcpListenAddress=3D"auto"
tcpListenPort=3D"4001" ##Using port 4002 on the other tomcat since both
instance on the same server
tcpSelectorTimeout=3D"100"
printToScreen=3D"false"
expireSessionsOnShutdown=3D"false"
useDirtyFlag=3D"true"
replicationMode=3D"pooled"
/>
 The following is the start up log from catalina.out
... ( following seems telling multicast works fine, tomcat joins the cluste=
r
member ship )
INFO: Cluster is about to start
Oct 24, 2005 5:01:57 PM org.apache.catalina.cluster.tcp.SimpleTcpClustersta=
rt
INFO: Sleeping for 2000 secs to establish cluster membership
Oct 24, 2005 5:01:57 PM
org.apache.catalina.cluster.tcp.SimpleTcpClustermemberAdded
INFO: Replication member added:org.apache.catalina.cluster.mcast.McastMembe=
r
[tcp://206.47.63.195:4001,206.47.63.195,4001, alive=3D38841]

.... ( following is a webapp /comstg which fails to receive session state i=
n
60s)
INFO: Processing Context configuration file URL
file:/app/ufs2/UfsServer/tomcat/conf/Catalina/localhost/comstg.xml
Oct 24, 2005 5:02:09 PM org.apache.catalina.cluster.session.DeltaManagersta=
rt
INFO: Starting clustering manager...:/comstg
Oct 24, 2005 5:02:09 PM
org.apache.catalina.cluster.tcp.SimpleTcpClustermessageDataReceived
WARNING: Context manager doesn't exist:/comqa
Oct 24, 2005 5:02:09 PM org.apache.catalina.cluster.session.DeltaManagersta=
rt
WARNING: Manager[/comstg], requesting session state from
org.apache.catalina.cluster.mcast.McastMember[
tcp://206.47.63.195:4001,206.47.63.195,4001, alive=3D38841]. This operation
will timeout if no session state has been received within 60 seconds
Oct 24, 2005 5:03:10 PM org.apache.catalina.cluster.session.DeltaManagersta=
rt
SEVERE: Manager[/comstg], No session state received, timing out.
 ... ( following is a webapp /comqa which successfully receives session
state in 106ms)
INFO: Processing Context configuration file URL
file:/app/ufs2/UfsServer/tomcat/conf/Catalina/localhost/comqa.xml
Oct 24, 2005 5:03:17 PM org.apache.catalina.cluster.session.DeltaManagersta=
rt
INFO: Starting clustering manager...:/comqa
Oct 24, 2005 5:03:17 PM org.apache.catalina.cluster.session.DeltaManagersta=
rt
WARNING: Manager[/comqa], requesting session state from
org.apache.catalina.cluster.mcast.McastMember[tcp://206.47.63.195:4001,206.=
47.63.195,4001,
alive=3D38841]. This operation will timeout if no session state has been
received within 60 seconds
Oct 24, 2005 5:03:17 PM org.apache.catalina.cluster.session.DeltaManagersta=
rt
INFO: Manager[/comqa], session state received in 106 ms.

------=_Part_6239_5445175.1130260506254--