Actually, the system we are concerned about will have tens of thousands of concurrent users. We are using a Java-based Single Sign On solution to tie together our various applications. Given that we have 30,000 students and another 5,000 - 7,000 faculty and staff, we can have a lot of activity.
Andrew R Feller, Analyst University Information Systems 200 Fred Frey Building Louisiana State University Baton Rouge, LA, 70803 (225) 578-3737 (Office) (225) 578-6400 (Fax) -----Original Message----- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 27, 2008 1:57 PM To: Tomcat Users List Subject: RE: Storing sessions to disk like Apache HTTP server > From: Andrew R Feller [mailto:[EMAIL PROTECTED] > Subject: RE: Storing sessions to disk like Apache HTTP server > > Some coworkers had concern that Java applications had difficulties > scaling due to session information kept within memory. Do you really think you're going to have tens of thousands of concurrent sessions? Or is your application designed to load up each session with megabytes of data? Rather than add complexity to handle what is likely a non-issue, why not take the simple and inexpensive route: run a 64-bit environment and add memory as needed. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
