There are two ways to fix this:
- Move your log4j classes into the Tomcat context (and not within your own
server context). Not very portable (you couldn't just drop 'n run the WAR
file)
- Change the static initializer in the
org.apache.log4j.nt.NTEventLogAppender in the following way:
static
{
try
{
System.loadLibrary ( "NTEventLogAppender" );
}
catch ( UnsatisfiedLinkError error )
{
// throw this one
throw error;
}
catch ( Exception oops )
{
// ignore this one
}
}
Can you tell me what exception you're getting in the stack trace?
-Chris
----- Original Message -----
From: "Koes, Derrick" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, July 10, 2002 6:28 AM
Subject: NT Event Viewer dll question
> I'm using log4j in my web app. I'm also using the dll that allows logging
> to the NT Event Viewer application log.
>
> However, I cannot use the manager servlet to undeploy and redeploy an
> updated version of my web app because of a stack trace produced that
states
> that the dll is already loaded.
>
> Is there any way to configure log4j/tomcat to check for this?
>
>
>
> Thanks,
>
> Derrick
>
>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
