----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
Hi all,
I use a simple servlet in order to pass requests to a large system that
manages users and their access to the database.
Servlet is "mapped" to a MySessionManager unique instance which again
delegates requests (according to a value of hidden mysessionid field) to
a right instance of MySession.
When a user clicks a button (eg next in a form) several times without
waiting for reply, i notice that the system is executing each of these
requests in sequential (queued) order (even if the user leaves the page
(closes the browser)).
My question is: Does the JServ create a new thread for each request (so
they wait their "turn" to execute) or is it reusing an existing thread
that is "bounded" to a particular HttpSession? If second is true, who is
then doing the request queuing and how can i control that (disable it)?
The point is: I dont want to allow the user to "hang-up" the whole
system by clicking on a large processing buttons many times without
waiting for them to bring up the reply. User should not be allowed to
make any requests while any of his/her previous requests is being
handled at that moment.
If there is no common procedure to this, I'll be forced to invoke some
javascript on each click that will disable future clicks in existing
page?
please help
thx
-SeJo
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search Archives:
<http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
