the way i handled this is with javascript.
on my save button i simply invoke a javascript function on the onclick
event. it checks a javascript page-scoped flag variable to see if save
button has been clicked or not. if it has, then i popup a message
saying "the previous submit is still being processed", otherwise i set
the flag variable and call form.submit(). this works even if they
press the browser "stop" button and then click the save button again.
basically, i'm doing the same thing as you are, but at the client-side
instead of the server side.
maybe there is a better way to handle this problem, but it has been
effective in my production app so far in belaying impatient users...
woodchuck
--- Jonathan Wilson <[EMAIL PROTECTED]> wrote:
> I need some good advice:
>
> I've got a production app running on a Redhat box that is having
> problems with the SAN which is causing all processes to slow/stall
> with
> heavy IO(CPU util is like 3%); the network/admin guys are working on
> that part but it's been ongoing. On two occasions during particularly
>
> heavy IO, TC 3.x stalls all threads while waiting for the SAN to
> respond
> (with file uploading/loading from SAN). Meanwhile a user is
> submitting a
> form, which takes too long for their taste, hits stop on the browser
> and
> submits again(and again...). I've got code to determine if they've
> submitted a form already, but that code doesn't get triggered till
> after
> the submit is actually handled by my servlet. So it may be 3/4
> submits
> before the locks are finally in place...Any idea how I can lock this
> down? Isolating TC from SAN is not an option.
>
> Thanks in advance,
> JW
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
__________________________________
Do you Yahoo!?
Yahoo! Small Business - Try our new resources site!
http://smallbusiness.yahoo.com/resources/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]