Sorry to break this open again after a month. My first attempt was to simply decrease the number of SQL connections made to the database, but if the user hammers the refresh they can still reproduce the issue. I haven't been able to figure a good way to handle it on the client side, most of the internet seems to be struggling with resubmitting information through a form my problem comes when loading the page with information from the database. Gaurav if you had a link to some documentation that would better explain your suggestion I would appreciate it. I would like to do like Source Forge does, if you hit the refresh too many times too fast they deny you access to the server. Can that be handled by the application?
Tomcat? Is that going to require a third party app?