Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
From: bugzilla@apache.org
To: dev@tomcat.apache.org
Subject: [Bug 54065] getResource with WARDirContext is very expensive
Date: Fri, 02 Nov 2012 12:15:22 +0000
Message-ID: <bug-54065-78-SZR1uWHMOZ@https.issues.apache.org/bugzilla/>
In-Reply-To: <bug-54065-78@https.issues.apache.org/bugzilla/>
References: <bug-54065-78@https.issues.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated
MIME-Version: 1.0

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

--- Comment #2 from Mark Struberg <struberg@yahoo.de> ---
Hi Mark!

Thanks for the tip with the ContextConfig.jarsToSkip. That worked out well! Of
course that also disables web-fragment parsing, right?

We have not been able to remove META-INF/resources though as this location is
used by other EE specs (e.g. JSF) since years. So there is practically no way
around this without breaking almost all JSF projects.

Thus I still think you should investigate the performance. It's sad that
servlet-3.0 requires to lookup resources in JNDI upfront. This is utter
expensive and really costs up to 20% of our performance. It's sad to see that
some EGs try to add as much features as possible without thinking about the
possible consequences. Maybe this can be solved via a negative cache
(remembering JNDI misses)? Or probably via an own configuration to disable this
behaviour? 

In my case it's pretty easy as we have all of our server environment under full
control ourselfs. But other developers cannot easily do this and thus would see
a major performance penalty.

-- 
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