Return-Path: 
 <dev-return-124291-apmail-tomcat-dev-archive=tomcat.apache.org@tomcat.apache.org>
X-Original-To: apmail-tomcat-dev-archive@www.apache.org
Delivered-To: apmail-tomcat-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 6B68998B5
	for <apmail-tomcat-dev-archive@www.apache.org>;
 Tue, 31 Jan 2012 23:06:10 +0000 (UTC)
Received: (qmail 71473 invoked by uid 500); 31 Jan 2012 23:06:09 -0000
Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org
Received: (qmail 71352 invoked by uid 500); 31 Jan 2012 23:06:08 -0000
Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@tomcat.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@tomcat.apache.org>
List-Post: <mailto:dev@tomcat.apache.org>
List-Id: <dev.tomcat.apache.org>
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Delivered-To: mailing list dev@tomcat.apache.org
Received: (qmail 71343 invoked by uid 99); 31 Jan 2012 23:06:08 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jan 2012 23:06:08 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.115] (HELO eir.zones.apache.org) (140.211.11.115)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Jan 2012 23:06:03 +0000
Received: by eir.zones.apache.org (Postfix, from userid 80)
	id 4D3F44FF02; Tue, 31 Jan 2012 23:05:43 +0000 (UTC)
From: bugzilla@apache.org
To: dev@tomcat.apache.org
Subject: DO NOT REPLY [Bug 52444] Classloading-based
 ServletContainerInitializer @HandlesTypes processing can result in long
 startup times
Date: Tue, 31 Jan 2012 23:05:41 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Tomcat 7
X-Bugzilla-Component: Catalina
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: guillaume.smet@gmail.com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: dev@tomcat.apache.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Changed-Fields: Status Resolution
Message-ID: <bug-52444-78-0cb44itLP9@https.issues.apache.org/bugzilla/>
In-Reply-To: <bug-52444-78@https.issues.apache.org/bugzilla/>
References: <bug-52444-78@https.issues.apache.org/bugzilla/>
X-Bugzilla-URL: https://issues.apache.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=52444

Guillaume Smet <guillaume.smet@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |

--- Comment #10 from Guillaume Smet <guillaume.smet@gmail.com> 2012-01-31 23:05:41 UTC ---
Hi Mark,

As we also had this problem with our application, we have built a Tomcat from
svn tip and when starting the application, we had the following stacktrace:
Caused by: java.lang.NullPointerException
    at
org.apache.tomcat.util.bcel.classfile.ClassParser.<init>(ClassParser.java:72)
    at
org.apache.catalina.startup.ContextConfig.populateJavaClassCache(ContextConfig.java:2132)
    at
org.apache.catalina.startup.ContextConfig.populateJavaClassCache(ContextConfig.java:2123)
    at
org.apache.catalina.startup.ContextConfig.checkHandlesTypes(ContextConfig.java:2058)
    at
org.apache.catalina.startup.ContextConfig.processAnnotationsStream(ContextConfig.java:2015)
    at
org.apache.catalina.startup.ContextConfig.processAnnotationsJar(ContextConfig.java:1904)
    at
org.apache.catalina.startup.ContextConfig.processAnnotationsUrl(ContextConfig.java:1872)
    at
org.apache.catalina.startup.ContextConfig.processAnnotations(ContextConfig.java:1858)

This is due to the fact that classes present in the jar files may implement
interfaces not present in the classpath (in our case, it's the optional commonj
support in Spring's scheduling classes which rises this problem).

We solved this problem by checking that the inputStream "is" is different from
null in populateJavaClassCache(String className).

With this fix, our application starts and the initialization is faster than
with 7.0.25.

HTH.

-- 
Guillaume

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org