Further info... I updated JCL to 1.0.4 and removed the org.apache.commons.logging.LogFactory file... logging broke again. I put the file back, restarted the app, and logging was once again working.
Log4J version is 1.2.8 incidentally, so I was almost up to date with that as well (have NOT updated to 1.2.9). Any ideas? I have no problem believing I don't have the right answer at this point, but it does certainly appear to be fixing the problem somehow. Thanks! -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Tue, April 12, 2005 1:28 pm, Frank W. Zammetti said: > Hi Ceki, > > I am using an older version, but not *that* old... 1.0.3 > > Would you expect that upgrading from 1.0.3 to 1.0.4 (the latest production > release I can see) and also removing the > org.apache.commons.logging.LogFactory file would result in my logging > still working as it does now with that file? > > I'm certainly willing to give it a try if you are telling that is the the > correct answer (you would know better than me certainly!) :) > > -- > Frank W. Zammetti > Founder and Chief Software Architect > Omnytex Technologies > http://www.omnytex.com > > On Tue, April 12, 2005 1:20 pm, Ceki G�lc� said: >> >> Frank, >> >> What you suggest sounds quite wrong to me. In particular, >> org.apache.commons.logging.impl.Log4jFactory is deprecated [1] and >> should >> not be used. The fact that setting org.apache.commons.logging.LogFactory >> gives positive results indicates that you may be using an old version of >> JCL as James suspected you were. >> >> [1] >> http://jakarta.apache.org/commons/logging/api/org/apache/commons/logging/impl/Log4jFactory.html >> >> At 06:07 PM 4/12/2005, Frank W. Zammetti wrote: >>>Thanks James, that did put me on the right track... just for the sake of >>>having an answer in the archives, what solved the problem for me is >>> adding >>>the following file... >>> >>>org.apache.commons.logging.LogFactory >>> >>>...(yes, that is the full filename!), with the contents... >>> >>>org.apache.commons.logging.impl.Log4jFactory >>> >>>... stored under META-INF/services in the root of the webapp (so that it >>>is part of the WAR within the EAR). >>> >>> >From what I gather, Websphere wants to take over logging with its >>>proprietary logging subsystem, and this basically tells it "No, no, bad >>>app server! Use what *I* say to use!" >>> >>>So, while not strictly a Log4J issue, I can see this coming up again for >>>others, so hope it helps someone down the road! >>> >>>-- >>>Frank W. Zammetti >>>Founder and Chief Software Architect >>>Omnytex Technologies >>>http://www.omnytex.com >> >> -- >> Ceki G�lc� >> >> The complete log4j manual: http://www.qos.ch/log4j/ >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
