First of all, I researched a lot about this problem and didn't find anything that would apply specifically to my problem.
Let me explain it. I have a project that uses Struts, EJB and JSP running on websphere (5.1.2). In a specific JSP page, there is a button that submit de request to an action. That takes a lot to run, about 2 minutes. My problem is that this action is being performed twice in an interval of 60 seconds between them. It is exactly 60 seconds, and always in the period in which the page is blocked, preventing any user action.
I already checked the most common errors in pages that do not contain the src tag, or '# links but they do not apply.
Anyone have any ideas to help?
Bear Bibeault wrote:Is there a meta refresh tag on the page causing a refresh? What about script?
Have you used an HTTP monitor to see if the request has any clues in it as to who/why it's being generated?
No, there is not. And the strangest thing is that this is only occurring for one user, and only in the testing environment. I run the application locally and this error never occurs on my server.
Oh, I forgot to mention that I checked the log, and saw that the request is initiated by a second thread, but contain the same data the first request sent.
But I'm not familiar with websphere application server configuration. My suspicion is that there is some service in some layer of the server that is storing the first request made, and submit it again after timeout. But I really don't know where is this configuration...
Matthew Freake wrote:Does the tester access the servlet via a proxy? I've had production issues where a proxy would re-request a URL if it took longer than a certain time period.
I second that!
We are facing problems with a new proxy that hogs the request. When using the dev-net we are accessing directly to servers and databases but on the test-net they use a local-fw -> proxy -> net-fw -> dev-net.
Temporary solution was to add the dev-net servers in "no proxy for...".
Weird or not? I doubt that I was the first one to have duplicate requests because this parameter...
Anyway.. thank you all!