All,
I've ran into a bug with a 3rd party app I use to monitor my tomcat server.
What is happening is that when I go to the log tab to view a list of
available logs the open file handlers spike, hitting ulimit on my
production and test servers, which causes breakage.
The app in question uses the following java to walk the classpath and look
for jars that may contain logging related configuration files.
private void interrogateContext(Context ctx, List allAppenders) {
Application application = ApplicationUtils.getApplication(ctx);
ClassLoader cl = ctx.getLoader().getClassLoader();
(full file can be found at
http://code.google.com/p/psi-probe/source/browse/trunk/core/src/main/java/com/googlecode/psiprobe/beans/LogResolverBean.java#203)
The understanding of the actual developer was that the jars would already
be loaded by the JVM and shouldn't need to be re-opened.
However, it almost seems as if instead of returning a reference to the
loaded jars on the classpath, a copy of the files is being returned, which
means having to re-open all the jars in addition to the actual log and log
configuration files in question.
I did some looking online, but what I found was either unclear to me,
unrelated or I didn't read it right.
Can someone please confirm how the Context's getLoader().getClassLoader()
behaves in this instance?
Thank you.
Lee Lowder
This communication and any attachments are confidential, protected by
Communications Privacy Act 18 USCS § 2510, solely for the use of the intended
recipient, and may contain legally privileged material. If you are not the
intended recipient, please return or destroy it immediately. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
