RE: tomcat load-balancing maintenance strategy?
Filip, Yes, That would be awesome. Thanks, Dan -Original Message- From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Fri 3/11/2005 2:11 PM To: Tomcat Users List Cc: Subject: Re: tomcat load-balancing maintenance strategy? its fixed in 5.5.x, you need a patch for 5.0.x? Dan Carwin wrote: I also experienced cluster failure when restarting a downed cluster member in 5.0. I tested with Tomcat 5.0.30. Randall, what version of Tomcat did you succeed with? Thanks, Dan -Original Message- From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 08, 2005 10:45 AM To: Tomcat Users List Subject: RE: tomcat load-balancing maintenance strategy? Jim, Also check the archives for my post on restarting a downed Tomcat cluster member. This was not working well prior to Tomcat 5.5.8. When the instance was restarted it would throw exceptions trying to re-synchronize vi session replication. - Richard -Original Message- From: Randall Svancara [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 08, 2005 9:40 AM To: Tomcat Users List Subject: RE: tomcat load-balancing maintenance strategy? You need to implement either in memory session replication or persist the session in a database or a shared file system. I have finally got my tomcat cluster working and session replication is functional. Randall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat load-balancing maintenance strategy?
I also experienced cluster failure when restarting a downed cluster member in 5.0. I tested with Tomcat 5.0.30. Randall, what version of Tomcat did you succeed with? Thanks, Dan -Original Message- From: Richard Mixon (qwest) [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 08, 2005 10:45 AM To: Tomcat Users List Subject: RE: tomcat load-balancing maintenance strategy? Jim, Also check the archives for my post on restarting a downed Tomcat cluster member. This was not working well prior to Tomcat 5.5.8. When the instance was restarted it would throw exceptions trying to re-synchronize vi session replication. - Richard -Original Message- From: Randall Svancara [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 08, 2005 9:40 AM To: Tomcat Users List Subject: RE: tomcat load-balancing maintenance strategy? You need to implement either in memory session replication or persist the session in a database or a shared file system. I have finally got my tomcat cluster working and session replication is functional. Randall - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Native session replication/failover in tomcat 5.0.30
I have the tomcat 5.0.30 replication partially working on redhat as3. Here's what I see: 1. both tomcats up 2. use tcrepl (provided by Richard Mixon) app to etablish session on one tomcat (verify by tailing log file) 3. kill that tomcat 4. session fails over to other tomcat successfully 5. Problems occur after bringing downed tomcat back up. When I start the tomcat instance that I had taken down I get three java errors during tomcat startup (listed below) 6. After the downed tomcat finally comes back up it causes the session to try to fail back over. But that fail over fails and the session croaks, resulting in 500 errors. (first error) Feb 22, 2005 3:49:46 PM org.apache.struts.util.MessageResourcesFactory createFactory SEVERE: MessageResourcesFactory.createFactory java.lang.ClassNotFoundException: org.apache.struts.util.PropertyMessageResourcesFactory (second error) Feb 22, 2005 3:50:16 PM org.apache.catalina.cluster.tcp.ReplicationTransmitter sendMessageData WARNING: Unable to send replicated message, is server down? java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) (third error) java.lang.ExceptionInInitializerError at sun.misc.Unsafe.ensureClassInitialized(Native Method) at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAcces sorFactory.java:20) at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:12 2) at java.lang.reflect.Field.acquireFieldAccessor(Field.java:779) at java.lang.reflect.Field.getFieldAccessor(Field.java:760) What is the expected behavior? Side note - differences between clustering in 5.0 and 5.5: 5.0 doesn't have the JvmRouteBinderValve 5.0 doesn't have the JvmRouteSessionIDBinderLifecycleListener 5.0 doesn't have StoreConfigLifecycleListener - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Session replication with jk 1.2.8
I'm setting up session replication in tomcat 5.0.30, using apache 2.0.52 with jk 1.2.8 as the LB mechanism. I'm currently failing to get sessions to stick to a tomcat instance. I used this article for a reference: http://www.javaworld.com/javaworld/jw-12-2004/jw-1220-tomcat.html But the author is doing it with jk2, and hasn't updated his article for jk config yet. He references the jvmRoute=servername variable which needs to match a like variable tomcatId in workers2.properties. Of course workers.properties doesn't have the tomcatId variable. The funny thing is in the change notes for the jk connector, I see that Bill Barker made some change referencing the jvmRoute variable: Check all JSESSIONID cookies for a valid jvmRoute. If you have multiple Tomcats with overlapping domains, then you can get multiple cookies without a defined order. This will route correctly as long as the different domains don't have any Tomcats in common. (billbarker) So I infer that somehow jvmRoute is now relevant in the jk conector, and if so there might be some need for a matching tomcatId variable. What is the syntax for these variables in the jk 1.2.8 world, and where do they go? (I am assuming jk2.properties does not exist) Current file syntax: Workers.properties worker.list=ajp13 worker.ajp13a.port=8009 worker.ajp13a.host=localhost worker.ajp13a.type=ajp13 worker.ajp13a.lbfactor=50 worker.ajp13b.port=8010 worker.ajp13b.host=localhost worker.ajp13b.type=ajp13 worker.ajp13b.lbfactor=50 worker.ajp13.type=lb worker.ajp13.balance_workers=ajp13a,ajp13b - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Need simple app to test tc5 session failover - please
Hello Tomcat users and creators. Thank you all for helping out. Can anyone point to me a simple app that I can use to test if tomcat 5 session failover is working? I don't think any of the standard tomcat examples will work. I tried numguess, but my guess count gets reset to 1 each time I fail over. I'm not a java programmer so I'm not able to write my own test app. I do know from the docs page that an app has to meet (at least) the following two requirements: 1. All your session attributes must implement java.io.Serializable 2. Make sure your web.xml has the distributable/ element I'm using tomcat 5.0.30 on linux. I have just set up jk-based load balancing and uncommented the cluster section in the server.xml. Thanks very much, [EMAIL PROTECTED]
RE: Tomcat 5 - coyote/jk2 connector defaults - maxthreads, timeout?
Resending...anyone know??? -Original Message- From: Dan Carwin Sent: Friday, November 05, 2004 11:01 AM To: [EMAIL PROTECTED] Subject: Tomcat 5 - coyote/jk2 connector defaults - maxthreads, timeout? what is the default maxThreads in tomcat 5 jk2/coyote connector? What is the default serverTimeout ? #channelSocket.serverTimeout=??? #channelSocket.maxThreads=??? (fwiw I'm referring to the version included in tc 5.0.28) Thanks, Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat 5 - coyote/jk2 connector defaults - maxthreads, timeout?
what is the default maxThreads in tomcat 5 jk2/coyote connector? What is the default serverTimeout ? #channelSocket.serverTimeout=??? #channelSocket.maxThreads=??? (fwiw I'm referring to the version included in tc 5.0.28) Thanks, Dan
JK2 sending directory listings to tomcat, it should not
There's a known bug in the jk connector: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25104 Which forwards directory requests to tomcat even when -ForwardDirectories is turned off. Testing jk2 I'm seeing the same behavior. Is there a known way to prevent directory listings from being forwarded to tomcat with jk2? [you cannot put JkOptions -ForwardDirectories into the apache conf with jk2] Does JK2 lack a way to prevent directory forwarding to Tomcat? Thanks, Dan Carwin [EMAIL PROTECTED] Recreation details: 1. set: DirectoryIndex index.html index.html.var home.html Default.htm Default.html index.jsp index.htm index.cgi Default.jsp 2. create empty directory under docroot. e.g. /htdocs/empty 3. specify in workers2.properties [uri:/*.jsp] info=mapping all jsp to tomcat 4. Visit empty directory, instead of dir listing or apache error, see a tomcat 500 error.
JkOptions -ForwardDirectories equivalent in JK2?
There's a known bug in the jk connector: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25104 Which forwards directory requests to tomcat even when -ForwardDirectories is turned off. So I have switched to jk2. Unfortunately I'm still getting the same behavior with JK2. Is there a known way to prevent directory listings from being forwarded to tomcat with jk2? [you cannot put JkOptions -ForwardDirectories into the apache conf with jk2] Thanks, Dan Carwin [EMAIL PROTECTED]
