This is an application level problem. You need to implement your own synchronization/locking system to prevent this from happening.
If you're running reports that are taking a while, you might want to consider creating a system that will email the results to the clients rather than making them wait. George Sexton MH Software, Inc. http://www.mhsoftware.com/ Voice: 303 438 9585 > -----Original Message----- > From: Chetan Chheda [mailto:chetan_chh...@yahoo.com] > Sent: Tuesday, December 15, 2009 9:04 AM > To: users@tomcat.apache.org > Subject: Limit user sessions in tomcat > > Hello, > > We frequently have situations where a user has brought down a > tomcat entirely by himself by running the same transaction multiple > times because the response was not quick enough. > > Is there a way through configuation of tomcat and mod_jk to control > the number of concurrent transactions/sessions a user can maintain? > Since this is something that can happen to anyone out there, I am > curious as to how you are handling this scenario.. > > Thanks, > Chetan > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
