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 "Edward Q. Bridges" <eb...@teachscape.com> on 2002/06/19 18:14:41 UTC
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>
Re: Strange weblogic problem with new jarfile name (WAS: Why is the version number included in the log4j jar file name?)
Posted by "Edward Q. Bridges" <eb...@teachscape.com>.
i will test, but be assured that this came after several hours yesterday late
afternoon and this morning of mine and another fellow's time -- most of it
waiting on weblogic restarts :)
this was also successfully reproduced on two different installations (our
individual development instances and on our central staging/testing instance --
which is clustered).
this was also reproduced in deploys using exploded war-files and intact war-
files.
i'd be more than happy to try other approaches at your (or anyone else's)
suggestion.
best regards
--e--
On Wed, 19 Jun 2002 18:29:57 +0200, Ceki Gülcü wrote:
> Edward,
>
> I personally tested the alpha and beta versions of log4j (but not 1.2
> final and later versions) under WL 6.1. So I find your discovery quite
> surprising. Can you please double check? I suggest that you remove the
> tmp directory and restart WL. Let us know if the problem persists.
>
> At 12:14 19.06.2002 -0400, Edward Q. Bridges wrote:
> >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
>
> --
> Ceki
>
>
> --
> 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>
Re: Strange weblogic problem with new jarfile name (WAS: Why
is the version number included in the log4j jar file name?)
Posted by Ceki Gülcü <ce...@qos.ch>.
Edward,
I personally tested the alpha and beta versions of log4j (but not 1.2
final and later versions) under WL 6.1. So I find your discovery quite
surprising. Can you please double check? I suggest that you remove the
tmp directory and restart WL. Let us know if the problem persists.
At 12:14 19.06.2002 -0400, Edward Q. Bridges wrote:
>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
--
Ceki
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>