You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Matt Cox <MC...@DeWolfe.com> on 2002/06/19 19:05:31 UTC
RE: Strange weblogic problem with new jarfile name (WAS: Why is t
he version number included in the log4j jar file name?)
Are you using WL 6.1 SP 2? I was looking at some threads on bea developer's
newsgroups where users where having problems with jars working in SP 1 but
not in SP 2. I wonder if this is related.
-----Original Message-----
From: Edward Q. Bridges [mailto:ebridges@teachscape.com]
Sent: Wednesday, June 19, 2002 12:37 PM
To: Michael Roytman
Cc: Log4J Users List
Subject: RE: Strange weblogic problem with new jarfile name (WAS: Why is
the version number included in the log4j jar file name?)
yes, the first example i provide is with log4j.jar named as such. when i
change
it back to log4j from the numbered name, and do a clean deploy it works once
again.
--e--
--Original Message Text---
From: Michael Roytman
Date: Wed, 19 Jun 2002 11:11:51 -0500
RE: Strange weblogic problem with new jarfile name (WAS: Why is the version
number included in the log4j jar file name?)
Have you tried renaming log4j-1.2.4.jar to log4j.jar and then re-deploying
it?
Michael
-----Original Message-----
From: Edward Q. Bridges [mailto:ebridges@teachscape.com]
Sent: Wednesday, June 19, 2002 11:15 AM
To: Log4J Users List
Subject: Strange weblogic problem with new jarfile name (WAS: Why is the
version number included in the log4j jar file name?)
we just upgraded log4j to the 1.2.4 jar.
we encountered a very very strange problem (using Weblogic 6.1), that seems
to
be
directly related to having the version number in the filename of the jar.
weblogic would fail upon access to a servlet that depended on log4j
(basically
every
servlet, since they all inherit from a class that contains an instance of
Logger
(used to
be Category)).
it would fail because it couldn't find the class, and yet, the
log4j-1.2.4.jar
file was
in WEB-INF/lib
upon closer examination, weblogic copies the jar files that a web-app is
dependent on
into its own special directory within WEB_INF, and mangles the names. to
illustrate,
here is the (edited) output of a find command in our deploy directory (our
web-
app is
named "ts2"):
bash-2.03$ find . -name '*.jar'
.
.
./ts2/WEB-INF/lib/log4j.jar
.
.
./ts2/WEB-INF/_tmp_war_edAdmin_edAdmin_ts2/WEB-INF/lib/log4j59854.jar
.
.
note that log4j.jar is mangled into log4j59854.jar.
now, after renaming log4j.jar to log4j.1.2.4.jar and clearing out the deploy
directory
and redeploying the web-application, this is what it looks like:
.
.
./ts2/WEB-INF/lib/log4j-1.2.4.jar
.
.
.
(all jars in the weblogic directory displayed):
./ts2/WEB-INF/_tmp_war_edAdmin_edAdmin_ts2/WEB-INF/lib/startup59860.jar
./ts2/WEB-INF/_tmp_war_edAdmin_edAdmin_ts2/WEB-INF/lib/jaxen-full59861.jar
./ts2/WEB-INF/_tmp_war_edAdmin_edAdmin_ts2/WEB-INF/lib/jdom59862.jar
./ts2/WEB-INF/_tmp_war_edAdmin_edAdmin_ts2/WEB-INF/lib/commons-
beanutils59863.jar
./ts2/WEB-INF/_tmp_war_edAdmin_edAdmin_ts2/WEB-INF/lib/soap59864.jar
./ts2/WEB-INF/_tmp_war_edAdmin_edAdmin_ts2/WEB-INF/lib/commons-
collections59865.jar
./ts2/WEB-INF/_tmp_war_edAdmin_edAdmin_ts2/WEB-INF/lib/saxpath59866.jar
note, that log4j-1.2.4.jar is now ignored, and i cannot execute a web
application.
now, i recognize that this is, in fact, a weblogic error and not a log4j
error.
but, i
mention it here because of the recent discussion regarding the name change,
in
case
anyone might come across a similar issue. has anyone else encountered this?
best regards
--e--
--
Edward Q. Bridges
http://www.teachscape.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
--
Edward Q. Bridges
http://www.teachscape.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>