|
Home > Archive > WebSphere Application Server > November 2005 > Duplicate (Empty) Request Fires Off After Two Minutes Issue
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Duplicate (Empty) Request Fires Off After Two Minutes Issue
|
|
|
| I was wondering if someone can shed some light on the issue we've been experiencing. We have a typical Web application scenario where a user submits a form to a Struts Action, which then calls a stored procedure. This stored procedure can, depending on
the parameters submitted, take a few minutes to complete. We have notices that on occasion, after the stored procedure has been running for a couple of minutes, another request comes in with all the fields set to their default values (as if the form's re
set() method had been called), causing a server-side runtime error. It does not seem that this duplicate request is triggered by the user submitting the form again, but rather that, for some reason, the App server is resubmitting an empty request (perhap
s after some kind of timeout has expired?).
One possible workaround calls for employing the Token Strategy to distinguish the original request from any duplicate ones and using a session scope flag to poll for when the original request is finished processing. However, we would still like to know w
hy something like this would be happening. Has anyone else come across a similar issue? Any suggestions would be greatly appreciated.
We are using Struts 1.0, J2EE 1.3, WebSphere App Server 5.1.x and Oracle 8i.
| |
| Ray McVay 2005-11-29, 5:59 pm |
| My experience has been that IE times out, Netscape/Mozilla reposts. This
was a few years ago doing form-based uploads.
mihajlo_jovanovic@bankone.com wrote:
> I was wondering if someone can shed some light on the issue we've
> been experiencing. We have a typical Web application scenario where
> a user submits a form to a Struts Action, which then calls a stored
> procedure. This stored procedure can, depending on the parameters
> submitted, take a few minutes to complete. We have notices that on
> occasion, after the stored procedure has been running for a couple of
> minutes, another request comes in with all the fields set to their
> default values (as if the form's reset() method had been called),
> causing a server-side runtime error. It does not seem that this
> duplicate request is triggered by the user submitting the form again,
> but rather that, for some reason, the App server is resubmitting an
> empty request (perhaps after some kind of timeout has expired?).
>
> One possible workaround calls for employing the Token Strategy to
> distinguish the original request from any duplicate ones and using a
> session scope flag to poll for when the original request is finished
> processing. However, we would still like to know why something like
> this would be happening. Has anyone else come across a similar
> issue? Any suggestions would be greatly appreciated.
>
> We are using Struts 1.0, J2EE 1.3, WebSphere App Server 5.1.x and
> Oracle 8i.
|
|
|
|
|