DO NOT REPLY [Bug 14042] - Memory leaks with JBoss 3.x +(Tomcat/Jetty)

[bu...@apache.org]

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

Memory leaks with JBoss 3.x +(Tomcat/Jetty)





------- Additional Comments From areus@ibit.org  2002-11-07 21:39 -------
I just found this in ActionServlet


    /**
     * Gracefully shut down this controller servlet, releasing any resources
     * that were allocated at initialization.
     */
    public void destroy() {

        if (log.isDebugEnabled()) {
            log.debug(internal.getMessage("finalizing"));
        }

        destroyApplications();
        destroyDataSources();
        destroyInternal();
        getServletContext().removeAttribute(Action.ACTION_SERVLET_KEY);

        // FIXME - destroy ApplicationConfig and message resource instances

    }

Could this be related with the bug?

In destroyApplications the RequestProcessor.destroy method is invoked on the
RequestProcessor of each ApplicationConfig, but the ApplicationConfig itself
(now ModuleConfigImpl) aren't processed

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