I have a web application that is hosted on an embedded device. This device has its own basic web server that can serve content just like any other web server.
The web application in question is pretty data hungry. It requests about 15 XML files (usually less than 1kb) every few seconds to update a wide variety of modules on the application page. This is done with jquery / ajax. Each module has an independent timer to update itself, usually every 5-10 seconds, so often these timers align and requests are done in bursts.
In long term tests, the web application begins to fail. Within a few hours, requests begin to fail, not due to timeouts, but due to web connection resets. Using Wireshark, it is evident that it is the browser requesting to reset the connection. I am able to look directly into the web server, and there are no errors/timeouts/resets/etc from the server end. It is directly the browser deciding to reset the connection.
I am in no way asking the browser to do this. My application is basic and is simply requesting data endlessly. I can't think of any reason for the browser itself to decide to reset the connection on its own. This occurs in firefox and chrome. My only suspects are myself and jQuery's AJAX.
Any ideas are appreciated.