Hola, >I'm trying to understand how a single instance of Tomcat manages sessions. >Is there any pooling/recycling of sesssion objects or are they >created/destroyed as required? >If they are pooled, is the size of this pool configurable?
They are not pooled. They are created and destroyed (and passivated, activated) as needed. You can configure how and where they're stored by adjusting the properties of the Manager element: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/config/manager.html You can also write a custom one of your own, which could pool sessions as you need. >Also where can I find some good documentation on managing sessions across a >cluster or load balanced instances? In the Clustering How-To document: http://jakarta.apache.org/tomcat/tomcat-5.0-doc/cluster-howto.html >Does anyone know of a practical limit for the number of concurrent >connections Tomcat can cope with on a reasonably out of the box Redhat >installation (obviously file descriptor limits aside)? It's limited by your hardware and things like the file descriptor limits. We routinely have hundreds of sessions, and I know of sites that are an order of magnitude higher. Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
