You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/03/06 11:13:56 UTC

DO NOT REPLY [Bug 6907] New: - jsp compiler not synchronized

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=6907>.
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=6907

jsp compiler not synchronized

           Summary: jsp compiler not synchronized
           Product: Tomcat 4
           Version: 4.0.2 Final
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Jasper
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: dylans@xs4all.nl


When X clients request the same jsp page, jasper tries to compile the
page X times ( assuming the page was not compiled before) this leads
to very high memory usage and potentially to out of memory errors (even
if memory would normally be sufficient for the expected load). Using jikes
as a compiler reduces the overall memory problem, but still swamps the 
processor as X copies are run at the same time.

Is this the expected behaviour?

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>