Duplicate request being sent to tomcat when trying to execute heavy loaded data.

[Deeps Mistry]

Hi,

Environment - tomcat 5.5
apache 2
Spring + Webworks+ hibernate

On performing a particular task which consists of heavily loaded data from the database, duplicate requests is being sent to the server.

I have Virtual Host + mod_jk implementation.
Also i have tested using Virtual Host+ mod_proxy, but still i am facing the same issue.

Is there any configuration on Tomcat/Apache side saying if "I do not receive any response , please resend the request" ?

Any thoughts ??

Many Thanks

[Tim Holloway]

Deeps Mistry wrote:
Is there any configuration on Tomcat/Apache side saying if "I do not receive any response , please resend the request" ?

No, because the HTTP protocol has no way to implement an option like that. HTTP is strictly one request/one-response per client request. No unsolicited server traffic.

[Deeps Mistry]

I have noticed a pattern on my server.

It sends the multiple request exactly after 3 minutes.

What does this indicate?

Thanks

[Tim Holloway]

It indicates that the client is re-submitting the request. You'll have to investigate the client to find out why, since HTTP servers don't send requests. Only responses.

[Deeps Mistry]

Tim Holloway wrote:It indicates that the client is re-submitting the request. You'll have to investigate the client to find out why, since HTTP servers don't send requests. Only responses.

I tried using Fiddler for investigating the client(browser), but i did not get any additional information.

How else can i investigate the client?


Thanks

[Tim Holloway]

The Firebug plugin for Firefox browser can display client requests and responses.

I have been known to use network sniffing tools such as tcpdump myself, but I tend to have more network savvy (and authority) than most software people do.

[Deeps Mistry]

Tim Holloway wrote:The Firebug plugin for Firefox browser can display client requests and responses.

I tried using Firebug as well...but no luck!!!


In my action class, i put thread.sleep for more than 3 minutes, and the result was -- > a new request exactly after 3 minutes.
So is this a client issue? or do i need to do some kind of a configuration on application side?

Thanks