om: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Sent: Friday, July 23, 2004 9:38 AM
>To: [EMAIL PROTECTED]
>Subject: AW: JDK compatibility
>
>We had a similiar problem, when someone unintentionally deployed a newer
>version of log4j (1.2.8, but we are still on 1.2.5) as a jar fi
We had a similiar problem, when someone unintentionally deployed a newer version of
log4j (1.2.8, but we are still on 1.2.5) as a jar file in the lib directory of a
webapplication. Depending on which application was called first (and thus initialized
our environment) sometimes the newer log4j c
