tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 45774] New: jspDestroy called after deployment, the second jspInit follows
Date Wed, 10 Sep 2008 14:58:28 GMT

           Summary: jspDestroy called after deployment, the second jspInit
           Product: Tomcat 5
           Version: 5.5.26
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Unknown

Created an attachment (id=22549)
 --> (
demo jsp and servlet with index.html. Install into $CATALINA_HOME/webapps

I am not sure if this is a duplicate of, but it sounds a bit
different and applies to 5.5.26.

The jsp is deployed without explicit web.xml definition, so it is loaded when
the first client request arrives. The call sequence is usually (but not always)
as follows:


This is hard to program around when using jspInit to set up a complex set of
background processes. They get torn down unnecessarily, only to be loaded up
immediately afterward. However, there is enough variability to make it
dangerous to assume the first jspDestroy will always be followed by jspInit -
it might be a REAL jspDestroy and the cleanup is really necessary.

I have attached a war that demonstrates the problem. There is an index.html
that will run either a demo servlet (which works properly with init/destroy) or
a demo jsp (which usually fails). The apps display the call sequence
graphically, but entries are also written to the catalina log file.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message