So, in those cases, I've built JavaScript logic running in the browser (in
the HTML file) that will set a boolean flag to block the second (and
subsequent) click(s). Is there a simple way to handle this server-side (I
can imagine the hard ways!), or does anyone know that the client side still
has holes I have not witnessed?
JT
<< Undoubtedly the user clicked twice on the button or link and
actually created two requests.>>
>
> Hi mail list,
>
> we encounter the following problem with Tomcat. From time to time a browser
> request seems to be handled by two threads from tomcat in parallel. Our own
> log from java servlets shows entries of different threads doing the same
> task for the same user, wich are just some milli secs apart. >>
