This next method call is the problem. I am sending a POST request from one
servlet instance to another one. But in situations with high load, all 20
instances are busy, so the ActiveRoleRemoval.sendLogoutMessages method which
sends the POST request blocks because there is no other instance/thread to
process the request.
Is this quite possible or nonsense?
It's possible although I would have thought the logout request would
have been queued up just like the external requets and just waited for a
moment for the next available thread and then continued. Regardless it
would probably be better to refactor your logout code away from the
other servlet to a class that can be called directly. Maybe a session
manager class that handles all things related to login an logout?
--David
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
