No session state received in 60s when tomcat cluster start up

[yuenlok]

I configured 2 tomcat instance running on the same server clustered with simple TcpClustering. The cluster message can trasfer between 2 nodes without problem, and the session replication works fine too. I can always shutdown the instance which serving the client, and the other instance takes over without affecting the transaction.

However, during the startup of the secondary tomcat, each application always has to wait 60seconds for the session state and time out with "SEVERE: Manager[/hqstg], No session state received, timing out". I really can't figure out why it sais the session state is not transfered while in fact the session duplication works fine. And how can I adjust this 60second time out setting?

Here's my cluster setup:
<Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
name="FilipsCluster"
debug="10"
serviceclass="org.apache.catalina.cluster.mcast.McastService"
mcastAddr="224.0.0.4"
mcastPort="45565"
mcastFrequency="500"
mcastDropTime="3000"
tcpThreadCount="6"
tcpListenAddress="206.47.xx.xx"
tcpListenPort="4001"
tcpSelectorTimeout="0"
printToScreen="false"
expireSessionsOnShutdown="false"
useDirtyFlag="true"
replicationMode="pooled"
/>

Thanks for any suggestions.