DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9120>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9120 JSPs "hang" for a short period Summary: JSPs "hang" for a short period Product: Tomcat 4 Version: 4.0.3 Final Platform: PC OS/Version: Linux Status: NEW Severity: Major Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I have several JSP pages specified in the XML view. Viewing them with the very same GET arguments they sometimes "hangs" for a short period of time. I "instrumented" the page to find out where it hangs (thinking it hangs in my own code somewhere), but I found that it "hangs" in different places within the page. When no such "hang" occurs, the thing takes 10ms max to complete. With the hang I get a consistent hang time ddepending on the page only. On some pages it is around 3 seconds, on another it is 5 seconds. The hangs occur _anwhere_ within the page. I already tried two different VMs: Blackdown 1.3.1_02a and Sun 1.3.1_03, both show the same problem. The pages are part of a very complex application, making heavy use of custom tag libraries, JDBC, JNDI (LDAP), Filters and about 200 custom classes. I tried to use a java profiling tool to attach to tomcat, but for some reason that doesn't work. I cannot deploy this application with the bug present, that is why I marked it "major". I should note that I have tried it on two completly different systems: A RH 6.2 based system and a RH7.3 based system (one running a 2.2 Kernel, the other running a recent 2.4 kernel). They have different glibc library versions but use the same java stuff. Both systems behave in the very same strange way. This makes me believe that it must be a tomcat problem. I could not come up with a simple test case. However, if I strip parts of the JSP page (reducing complexity) hanging occurs less often and does not take that much time. I honestly do not know what can cause this, however after taking the time measurements, I do not think it is my code... The problem exists with both the WARP (through apache) and the HTTP connector, BTW. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>