Very very small may be acceptable, what do you mean by very very small...?
Would 30,000 unique sessions across 3 servers.... have a potential issue?
Thanks.
Eric
Filip Hanik - Dev Lists wrote:
while there is a risk for duplicate sessions being generated, we
believe it to be very very small.
What you can do is set jvmRoute in the <Engine> element to be unique
for each one, that makes it less likely to be duplicate.
Or you can come up with a better random algorithm, take a look at
org.apache.catalina.session.StandardManager
Filip
Eric Waite wrote:
This has been addresses before I am sure, but I do not know where to
find the answer.
I have 3 Tomcat servers sitting behind a load balancer using sticky
sessions.
I do not have session replication working yet, the tomcats are
standalone.
How do I prevent and what are the chances that a duplicate session
id is generated?
Thanks in advance.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Eric Waite
[EMAIL PROTECTED]
Taylor Associates
Phone: (631) 549-3000
Fax: (631) 549-3156
1-800-732-3758 Ex 317
Http://www.readingplus.com
Need Help, Visit our support website: http://www.readingplus.com/support/
Learn how to use Reading Plus http://www.readingplus.com/help/
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
