jspDestroy and Tomcat 3.2 buggy

[Jason Novotny <JD...@lbl.gov>]

When using Tomcat 3.1 I had an initialization page that made use of the
jspInit() and jspDestroy() methods to initialize and destroy a server pool like
the following:


<%! static public Pool pool = null;
<%!  public void jspInit() {
        System.out.println("JSP init");
        pool = Pool.getInstance();
     }
%>

<%!  public void jspDestroy() {
        System.out.println("JSP destroy");
        if (pool != null) {
                pool.destroy();
        }
     }
%>

    Now, however when using Tomcat 3.2 it doesn't print out "JSP destroy" when
I shut down Tomcat like it used to- furthermore it doesn't look like the
resources are being freed. Has anyone else encountered this- or  is there a
workaround to storing application scope data that can be destroyed (receive an
event) when Tomcat shuts down?

    Thanks, Jason

--
Jason Novotny               novotny@george.lbl.gov
Home: (510) 704-9917        Work: (510) 486-8662
NERSC Distributed Computing http://www-didc.lbl.gov