Sign In/My Account | View Cart  

advertisement

AddThis Social Bookmark Button

Article:
  JSP Progress Bars
Subject:   Too much of this gets HTTP 503 in Tomcat
Date:   2004-07-12 06:52:04
From:   dulds
I have used this technique. Quite useful. However, the application I used it on had a very heavy task that required minutes [ had to do different database calls for validating records read from a file ]. The problem is, I had about 10,000 records. I had to see up to 25% of it done (after about 4 to 5 mins or so) and then Tomcat gives out an HTTP 503 - Service Unavailable.


I read in Tomcat docs [ somewhere ] that Tomcat has a "defense mechanism", it "takes out" a JSP/Servlet that is continually bombarded by "requests" [ continous character stream ].


I had to change the "Javascript" timing [ 1 second in example] three times [ 3, 6 and 8 seconds] and still get the same error. So I stopped working for now and try 10 seconds or more tomorrow till I get the timing right.