Thanks Andrew.
In answer to your question, some of our app requires SSL -- exactly like an order-style app (but it's not a product ordering app).
So, a person's session might involve the following path:
1. non SSL req 2. non SSL req 3. SSL req 4. non SSL req
and we'd like that entire session to be persistent (i.e., sticky with one particular app server). BTW, it is not an issue for us if that server fails during the session. It will happen rarely and it's an acceptable failure for us (i.e., not mission critical data).
I should have mentioned that we expect 1000 req/hour with this app. However, our app is not necessarily quick (dependent on external resources) and does keep a lot of state.
I'm personally someone in favor of a H/W LB solution, but looking to be convinced that a valid S/W solution exists which is better (or just as good) as a H/W solution. I know the S/W solution will be less reliable (not solid state), but I'm looking to hear from folks who have done SSL session affinity with a S/W only approach.
Thanks again,
From: Andrew Miehs <[EMAIL PROTECTED]> Reply-To: "Tomcat Users List" <[email protected]> To: "Tomcat Users List" <[email protected]> Subject: Re: Load balancing SSL sessions Date: Tue, 22 Feb 2005 22:40:14 +0100
We use F5 BigIPs, but they are probably overkill for your application - The cisco probably will be as well.
A 'Cheap' software solution might be to work with redirects, and 2 separate IP addresses.
ie: ssl1.mysite.com and ssl2.mysite.com - You will need 2 ssl keys though for this to work.
Does all of your app require ssl? or just a certain part, ie: payment. Do you need the stickiness
for the whole app? or just for the ssl (seeing you are using tomcat, you will probably need it for the whole app)...
Andrew
On Feb 22, 2005, at 10:24 PM, Kelly Vista wrote:
Hi -
We are looking to deploy our app, running on Tomcat 5, soon and are exploring load balancing options. We are looking at H/W and S/W solutions, and I was wondering if anyone had any past experience/advice they would like to share.
Our deployment is as pretty run-of-the-mill as it gets: 2 machines, each running Tomcat. We would like to avoid replicating state (since we have a lot of state in these apps, for reasons beyond our current control). Even in-memory session replication would not be option here, so we're punting on the Tomcat cluster solution.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
