Thanks Filip, I got some logging, but far more than is useful to try and debug what session replication is going on. If I switch to a recent (nightly?) build, will I be able to add debugging specifically for the clustering? (by adding a Logger child element to Cluster in server.xml?)
Up to now I've been trying to see what's going on by watching the replication packets over the network. I added a custom HttpSessionAttributeListener/HttpSessionListener to my webapp (via a listener element in my web.xml) and I'm not seeing any session events although I am seeing replication data being passed between the two servers. I'm using the DeltaManager so my assumption was that I shouldn't be. Any ideas? Please let me know what other info would be useful to paint a more complete picture! Sam. -----Original Message----- From: Filip Hanik - Dev [mailto:[EMAIL PROTECTED] Sent: 05 May 2004 16:48 To: Tomcat Users List Subject: log4j logging in Tomcat WAS: Clustering with 5.0.19 you need to enable it at the logger level, the code is currently logging with Log.info/Log.debug etc You can make is use log4j and do it using the log4j conf file http://jakarta.apache.org/commons/logging/guide.html To make some simple steps, I remember there was thread on this last week, not sure if they got it to work so here are the steps, let me know if you have problems 1. Download latest log4j package 2. Put the log4j-1.2.8.jar (or whatever name it is) in your $CATALINA_HOME/bin 3. In catalina.sh/catalina.bat add the log4j to the system classpath 4. in catalina.sh/catalina.bat, on the top add the JAVA_OPTS setting like this JAVA_OPTS="-Dlog4j.debug -Dlogj4.configuration=$CATALINA_HOME/bin/log4j.prop erties" 5. Put your log4j.properties file in CATALINA_HOME/bin of course, if you are on windows you will need to change / for \ and $ for %% but I am sure you can figure that for yourself :) Filip ----- Original Message ----- From: "Sam Lawrence" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Wednesday, May 05, 2004 10:00 AM Subject: RE: Clustering with 5.0.19 Thanks Filip, Do you know if there is any way I can get some debug info from 5.0.19? I'd feel happier going with a release build if possible. Kind regards, Sam. -----Original Message----- From: Filip Hanik - Dev [mailto:[EMAIL PROTECTED] Sent: 05 May 2004 15:31 To: Tomcat Users List Subject: Re: Clustering with 5.0.19 useDirtyFlag is not used with the DeltaManager, only with the SimpleTcpReplicationManager. As the name suggest, the DeltaManager only replicates deltas, and hence it can only replicate when the session is dirty. The clustering configuration has changed a little bit since 5.0.19, to make it more modularized. Also, the debug flag is a thing of the past, the clustering module is currently using the commons logger, same way all the other components are using it. Filip ----- Original Message ----- From: "Sam Lawrence" <[EMAIL PROTECTED]> To: "Tomcat" <[EMAIL PROTECTED]> Sent: Wednesday, May 05, 2004 9:26 AM Subject: Clustering with 5.0.19 Hi, I've successfully clustered two instances of Tomcat on different machines and I'm now trying to do some fine tuning on a struts based site. I want to make sure that the session is only being replicated when it needs to be. I have useDirtyFlag="true" although I'm not sure that it isn't still being re-sent after every request. I have the following Cluster element in my server.xml - <Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster" managerClassName="org.apache.catalina.cluster.session.DeltaManager" expireSessionsOnShutdown="false" debug="10" printToScreen="true" useDirtyFlag="true"> Although I have the debug/printToScreen attributes, I'm not seeing any debug information about session replication. How can I get some debug info? Any help greatly appreciated! Thanks, Sam Lawrence --------------------------------------------------------------------- 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] --------------------------------------------------------------------- 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]
