Add to the weirdness. Following
http://tomcat.apache.org/tomcat-5.5-doc/logging.html I decided to try
and enable log4j logging in Tomcat itself via
commons/classes/log4j.properties and common/lib/log4j-1.2.8.jar,
figuring it would help me narrow it down. This, *too* causes Tomcat to
hang, at this point here:
.2006-07-02 07:27:08,165 [main] DEBUG
org.apache.catalina.loader.WebappClassLoader .loadClass - Loading
class from local repository
.2006-07-02 07:27:08,165 [main] DEBUG
org.apache.catalina.loader.WebappClassLoader .loadClass -
loadClass(com.sun.el.ValueExpressionLiteral, false)
.2006-07-02 07:27:08,165 [main] DEBUG
org.apache.catalina.loader.WebappClassLoader .loadClass - Searching
local repositories
.2006-07-02 07:27:08,165 [main] DEBUG
org.apache.catalina.loader.WebappClassLoader .findClass -
findClass(com.sun.el.ValueExpressionLiteral)
.2006-07-02 07:27:08,165 [main] DEBUG
org.apache.catalina.loader.WebappClassLoader .findClass -
findClassInternal(com.sun.el.ValueExpressionLiteral)
.2006-07-02 07:27:08,165 [main] DEBUG
org.apache.catalina.loader.WebappClassLoader .loadClass -
loadClass(java.io.Externalizable, false)
.2006-07-02 07:27:08,165 [main] DEBUG
org.apache.catalina.loader.WebappClassLoader .findClass -
Returning class class com.sun.el.ValueExpressionLiteral
.2006-07-02 07:27:08,165 [main] DEBUG
org.apache.catalina.loader.WebappClassLoader .findClass - Loaded
by WebappClassLoader
delegate: false
repositories:
/WEB-INF/classes/
----------> Parent Classloader:
[EMAIL PROTECTED]
.2006-07-02 07:27:08,175 [main] DEBUG
org.apache.catalina.loader.WebappClassLoader .loadClass - Loading
class from local repository
I note that it occurs during the EL loading, could it be an EL <-> log4j
conflict?
Boris Unckel wrote:
> Hello Avi,
>
> Avi Deitcher wrote:
>
>> Bob,
>>
>> Thanks. Unfortunately, I am running it on my laptop (Windows) where I
>> need to keep it for now as a dev environment. I run a small consulting
>> business, this is an "on the side" product that need to be run whenever
>> I can catch time.
>>
>> I would love to be able to get Tomcat to tell me what it is doing, but I
>> am afraid that enabling logging in Tomcat itself might pollute the
>> environment and make the problem worse.
>>
>> Ironically, Tomcat has neither log4j nor commons-logging in its
>> $TOMCAT_HOME/common/lib nor server/lib, which makes me wonder how it is
>> using commons-logging in its own classes at all....
>
> by default the internal logging of Tomcat 5.5 is done via
> commons-logging to Tomcat-juli, which
> itself is a java.util.logging implementation.
> If you remove any direct log4j calls from your webapp and configure
> apache-tomcat-5.5.16\conf\logging.properties
> properly, you will use the same system by default.
>
> Have a look at:
> http://tomcat.apache.org/tomcat-5.5-doc/logging.html
> http://tomcat.apache.org/faq/logging.html
> http://jakarta.apache.org/commons/logging/
> http://jakarta.apache.org/commons/logging/commons-logging-1.1/troubleshooting.html
>
> http://wiki.apache.org/jakarta-commons/Logging
>
> Maybe you are interested in a more extended version:
> http://www.x4juli.org
>
> Regards
> Boris
>
> ---------------------------------------------------------------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
______________________________
Avi Deitcher
[EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
