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/07/08 20:15:54 UTC

DO NOT REPLY [Bug 10563] New: - Multiple compiles for multiple requests

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

Multiple compiles for multiple requests

           Summary: Multiple compiles for multiple requests
           Product: Tomcat 4
           Version: 4.1.6
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Jasper 2
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: gregw@mortbay.org


If multiple requests are presented for the same JSP at the same time, then
multiple instances of org.apache.jasper.compiler.JspCompiler are created and
multiple javac compilations are started at the same time.

While this eventually gives the correct results, it can make start up of a
JSP site very slow in the presences of live traffic (and the user is JspC
resistant for some unknown reason?)

I have tested a simple fix of synchronizing on a static in
org.apache.jasper.compiler.Compiler.compile:

        if (!isOutDated())
            return false;
        synchronized(Compiler.class)
        {
            if (!isOutDated())
                return false;


and it appears to work OK - but may not be optimal?

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