Filip, Thanks for your reply. Each app has identical web.xml files:
<?xml version="1.0" encoding="ISO-8859-1"?> <!-- Required in order to have default EL support --> <web-app xmlns="http://java.sun.com/xml/ns/j2ee"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee web-app_2_4.xsd" version="2.4"> <distributable/> <!-- General description of your web application --> <display-name>NAHRGIS Clustered</display-name> <description> NAHRGIS GIS Application </description> ... The context, with datasources and other resources, works as expected (but it lives in conf/Catalina/localhost/nahrgisdev.xml, not in server.xml). The cluster is set as follows: <Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster" managerClassName="org.apache.catalina.cluster.session.DeltaManager" expireSessionsOnShutdown="false" useDirtyFlag="false"> <Membership className="org.apache.catalina.cluster.mcast.McastService" mcastAddr="228.0.0.4" mcastPort="45564" mcastFrequency="500" mcastDropTime="3000"/> <Receiver className="org.apache.catalina.cluster.tcp.ReplicationListener" tcpListenAddress="10.0.0.1" tcpListenPort="4001" tcpSelectorTimeout="100" tcpThreadCount="6"/> <Sender className="org.apache.catalina.cluster.tcp.ReplicationTransmitter" replicationMode="pooled"/> <Valve className="org.apache.catalina.cluster.tcp.ReplicationValve" filter=".*\.gif;.*\.js;.*\.jpg;.*\.htm;.*\.html;.*\.txt;"/> <Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer" tempDir="/tmp/war-temp/" deployDir="/tmp/war-deploy/" watchDir="/tmp/war-listen/" watchEnabled="false"/> </Cluster> After further testing, one node consistently times out upon reload: requesting session state from org.apache.catalina.cluster.mcast.McastMember[tcp://10.0.0.2:4001,10.0.0 .2,4001 ... SEVERE: Manager[/nahrgisdev], No session state received, timing out While the other one gets it in 100 or so ms. Respectfully, Ivan. -----Original Message----- From: Filip Hanik - Dev [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 29, 2004 4:17 PM To: Tomcat Users List Subject: Re: Clustering and session replication org.apache.catalina.cluster.tcp.SimpleTcpCluster messageDataReceived WARNING: Context manager doesn't exist:/nahrgisdev this is telling you that the server that spits out this message does not have a <distributable/> context configured by the name "nahrgisdev" all the servers in the cluster must have the all the "<distributable/>" webapps configured identically Filip ----- Original Message ----- From: "Ivan Vasquez" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, September 29, 2004 3:03 PM Subject: Clustering and session replication We are having some problems with a cluster of 2x Tomcat 5.0.28 (JDK 1.4.2) regarding session replication. The problem manifests after a distributable application is reloaded. From that point on, a successful login to our application causes the same page to be reloaded by the other node (mod_jk is load balancing) as if no progress was being done. A new session ID is generated every time by either node. Every time it happens, the log shows: org.apache.catalina.cluster.tcp.SimpleTcpCluster messageDataReceived WARNING: Context manager doesn't exist:/nahrgisdev On application reload, a node shows this error Sep 29, 2004 3:47:26 PM org.apache.catalina.cluster.session.DeltaManager start WARNING: Manager[/nahrgisdev], requesting session state from org.apache.catalina.cluster.mcast.McastMember[tcp://128.192.104.11:4001, 128.192.104.11,4001, alive=253140]. This operation will timeout if no session state has been received within 60 seconds Sep 29, 2004 3:48:26 PM org.apache.catalina.cluster.session.DeltaManager start SEVERE: Manager[/nahrgisdev], No session state received, timing out. However, we can telnet the other side on that port. Internal NICs are not configured for the cluster because initially we thought they were the problem. The application's context is stored in conf/Catalina/localhost/nahrgisdev.xml. Of course, the application works well in a non-clustered environment. Thanks for any advice, Ivan. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
