Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 98296 invoked from network); 13 Sep 2000 06:10:27 -0000 Received: from adsl-63-198-47-229.dsl.snfc21.pacbell.net (HELO costin.dnt.ro) (63.198.47.229) by locus.apache.org with SMTP; 13 Sep 2000 06:10:27 -0000 Received: from localhost (costin@localhost) by costin.dnt.ro (8.9.3+Sun/8.9.1) with ESMTP id XAA03542 for ; Tue, 12 Sep 2000 23:12:06 -0700 (PDT) From: cmanolache@yahoo.com X-Authentication-Warning: costin.dnt.ro: costin owned process doing -bs Date: Tue, 12 Sep 2000 23:12:05 -0700 (PDT) X-Sender: costin@costin.dnt.ro To: "'tomcat-dev@jakarta.apache.org '" Subject: RE: Where should LoadOnStartupInterceptor go in server.xml In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N > However, I noted that when loadJSP() in LoadOnStartupInterceptor.java > calls "request.getSession(true)" it triggers the long initialization for > session ID generation. I agree - it shouldn't call getSession( true ). > I wouldn't think the precompile and preload of a JSP would need a > session ID. Do you have a problem removing this getSession() call for > Tomcat 3.2 and/or 3.3? I didn't see any problems when testing this. +1 to remove it. I think it's almost a bug if the code calls getSession to pre-compile or init servlets. ( the way jasper is interfaced with tomcat is a hack. If anyone has time to take a look a JspInterceptor, it may improve this ). Costin ( I have a deadline on 20, sorry if I can't contribute too much until then)