Hi, The problem is we need to deploy an application to 3-400 users. Currently the application is being used by significantly less users on a reasonably beefy machine but that machine is really the server for something else so we'd like to get tomcat off of it.
Our plan is to use several single processor machines but the question would be how the users would access these. So my questions are below. Obviously clustering the tomcats would be a good option, my one question on this would be, do the sessions have to be fully serializable to be shared across the tomcat instances? Another option would be to load balance using either the built in tomcat load balancer or the JK2 connector. My question here would be, is either of these stateful, ie do they keep track of which tomcat a particular user is using. Also pros and cons of either of these methods would be appreciated. Thanks Matt
Any opinions expressed in this E-mail may be those of the individual and not necessarily the company. This E-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this E-mail in error and that any use or copying is strictly prohibited. If you have received this E-mail in error please notify the beCogent postmaster at [EMAIL PROTECTED] Unless expressly stated, opinions in this email are those of the individual sender and not beCogent Ltd. You must take full responsibility for virus checking this email and any attachments. Please note that the content of this email or any of its attachments may contain data that falls within the scope of the Data Protection Acts and that you must ensure that any handling or processing of such data by you is fully compliant with the terms and provisions of the Data Protection Act 1984 and 1998.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
