Hello Justin,
Thanks for your response. My understanding is that there will be
multiple instances of a servlet depending on what the container thinks
is necessary. This will most likely happen, because this is a high-volume
site. If that's the case, won't there be multiple instances of the
serv
Here's a thread that's discussing the same problem. Though it's referring
to the use made in the Struts code, and I'm just talking about a small
synchronize call, it's essentially the same issue. If the best way is to
synchronize on an object that's in the session, how do you properly get
that ob
Hi Stefan,
Thanks for the explanation. That makes sense, except how can you make
sure that the object is added to the session only once, when the session
is created?
It would seem like you would need to synchronize on something else for
adding the object to the session, because there might be a
Hello,
We are trying to prevent the "multiple submission of a form problem",
that can result when a user double-clicks the submit button. We have a
process in place, but we have been unable to get the session based
synchronization to work correctly.
Our order page submits to a "meta-refresh" pag
