Thanks for the links. The 'dot in the filename' has caught me before so I made sure that I named the file log4j.jar. I am deploying my app as a war file. I have not tried flushing the .wlnotdelete directory.
After doing a little more experimentation I discovered that I had made an error in my original post. If the log4j.jar is in my WEBINF/lib directory and ... commons-logging.properties is (empty) then NoClassDefFoundError ---------------- commons-logging.properties is org.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog then no error ---------------- commons-logging.properties is org.apache.commons.logging.LogFactory=org.apache.commons.logging.impl.Log4jFactory then NoClassDefFoundError ----------- So it must be some sort of class loading error. I wonder if there is a way to determine my classpath at runtime? On 2/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Could there be something outside your app that's using commons logging, > and therefore needs log4j once it's installed? Try putting the > log4j.jar in your server classpath, e.g., weblogic81/server/lib, and see > if that helps. I'm really grasping at straws, here. > > Alternatively, could there be another log4j.jar in the server classpath? > See http://forums.bea.com/bea/message.jspa?messageID=200071715&tstart=0 > and http://forums.bea.com/bea/message.jspa?messageID=200071922&tstart=0 > > Is your jar named "log4j.jar" and not something else? I turned up a > this > (http://forums.bea.com/bea/message.jspa?messageID=200060394&tstart=0) > related to WLS 7.0. > > Have you tried flushing out the .wlnotdelete directory? We've had > numerous issues with WLS deciding that it didn't need to deploy the new > code because it thought the previously deployed version was good enough. > > Have you looked in the server log (either in the console that starts the > server or through the management console), to see if there are any > clues? > > Are you deploying this as a .war file or .ear file? > > - George > > > > -----Original Message----- > > From: J T [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, February 01, 2006 4:40 PM > > To: Struts Users Mailing List > > Subject: Re: Just adding log4j.jar to struts 1.2.7 project > > under weblogic causes stack trace > > > > > > yes using > > > > /opt/bea/wls_sp2/jdk141_05 > > > > > > > > > > On 2/1/06, [EMAIL PROTECTED] > > <[EMAIL PROTECTED]> > > wrote: > > > > > > Are you using the jdk that comes with WebLogic? Under > > WebLogic 8.1.2, > > > that was in C:\bea\jdk141_05 for my installation. WebLogic > > plays some > > > intricate games with the ClassLoader. > > > > > > > -----Original Message----- > > > > From: J T [mailto:[EMAIL PROTECTED] > > > > Sent: Wednesday, February 01, 2006 4:27 PM > > > > To: Struts Users Mailing List > > > > Subject: Re: Just adding log4j.jar to struts 1.2.7 project under > > > > weblogic causes stack trace > > > > > > > > > > > > I agree that it is weird. We have log4j.jar in other applications > > > > deployed on the server (not struts based > > > > applications) and they work ok. We are using jdk14_05. > > > > > > > > All I need is a logger that will write to a file. I don't think > > > > SimpleLog will do that so I guess log4j is the only other option. > > > > > > > > > > > > On 2/1/06, [EMAIL PROTECTED] > > > > <[EMAIL PROTECTED]> > > > > wrote: > > > > > > > > > > None that are related to log4j. > > > > > > > > > > It's curious that your stack trace doesn't name the class > > > > that can't > > > > > be instantiated. What version of Java are you using? This > > > > might be a > > > > > question for BEA. > > > > > > > > > > - George > > > > > > > > > > > -----Original Message----- > > > > > > From: J T [mailto:[EMAIL PROTECTED] > > > > > > Sent: Wednesday, February 01, 2006 3:55 PM > > > > > > To: Struts Users Mailing List > > > > > > Subject: Re: Just adding log4j.jar to struts 1.2.7 > > project under > > > > > > weblogic causes stack trace > > > > > > > > > > > > > > > > > > The jguru link you provided did not work for me. I > > was using the > > > > > > file appender so I don't think that I need anything else. > > > > What libs > > > > > > are in your WEB-INF/lib directory? > > > > > > > > > > > > On 2/1/06, [EMAIL PROTECTED] > > > > > > <[EMAIL PROTECTED]> > > > > > > wrote: > > > > > > > > > > > > > > I've used log4j 1.2.9 with struts 1.2.7 and Weblogic 8.1.2 > > > > > > without any > > > > > > > problems. Do you have any indication of what class is > > > > not being > > > > > > > found? Are you missing a dependency for an appender that > > > > > > you're using? > > > > > > > (See http://www.jguru.com/faq/view.jsp?EID=1007095, though > > > > > > this may be > > > > > > > out-of-date.) > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: J T [mailto:[EMAIL PROTECTED] > > > > > > > > Sent: Wednesday, February 01, 2006 9:57 AM > > > > > > > > To: user@struts.apache.org > > > > > > > > Subject: Just adding log4j.jar to struts 1.2.7 > > project under > > > > > > > > weblogic causes stack trace > > > > > > > > > > > > > > > > > > > > > > > > I would like to use log4j for logging under struts. As > > > > > > soon as I add > > > > > > > > the log4j.jar to my WEB-INF/lib directory (I tried > > > > > > 1.2-13, 1.2-12, > > > > > > > > 1.2-8, etc) and try to access the application I get a 500 > > > > > > internal > > > > > > > > error (below). When I remove it my app runs normally. I > > > > > > have tried > > > > > > > > using log4j.properties & commons-logging.properties both > > > > > > > > with and without the jar present and no logs were produced > > > > in any of > > > > > > > > the cases. > > > > > > > > > > > > > > > > Any thoughts on why this is happening? Is there a > > > > log4j version > > > > > > > > recommended for struts 1.2.7? I only want a logging > > > > > > framework that > > > > > > > > can write to a file and I don't think SimpleLog > > can do that. > > > > > > > > > > > > > > > > Versions > > > > > > > > Struts 1.2.7 > > > > > > > > lo4j - various > > > > > > > > weblogic - 8.1.2.0 > > > > > > > > > > > > > > > > Error 500--Internal Server Error > > > > > > > > > > > > > > > > java.lang.NoClassDefFoundError > > > > > > > > at sun.reflect.GeneratedConstructo > > > > > > > > rAccessor191.newInstance(Unknown > > > > > > > > Source) > > > > > > > > at > > > > > > > > sun.reflect.DelegatingConstructorAccessorImpl.newInstance( > > > > > > > > DelegatingConstructorAccessorImpl.java:27) > > > > > > > > at > > > > > > > > java.lang.reflect.Constructor.newInstance(Constructor.java:274) > > > > > > > > at java.lang.Class.newInstance0(Class.java :306) > > > > > > > > at java.lang.Class.newInstance(Class.java:259) > > > > > > > > at > > > > > > > > > > > > weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run( > > > > > > > > ServletStubImpl.java:991) > > > > > > > > at > > > > weblogic.security.acl.internal.AuthenticatedSubject.doAs > > > > > > > > ( > > > > > > > > AuthenticatedSubject.java:317) > > > > > > > > at > > > > > > > > > > > > > > > > > > > > weblogic.security.service.SecurityManager.runAs(SecurityManager.java > > > > > > > > :118) > > > > > > > > at > > > > weblogic.servlet.internal.ServletStubImpl.createServlet( > > > > > > > > ServletStubImpl.java:869) > > > > > > > > at > > > > weblogic.servlet.internal.ServletStubImpl.createInstances > > > > > > > > ( > > > > > > > > ServletStubImpl.java:848) > > > > > > > > at > > > > weblogic.servlet.internal.ServletStubImpl.prepareServlet( > > > > > > > > ServletStubImpl.java:787) > > > > > > > > at > > weblogic.servlet.internal.ServletStubImpl.getServlet( > > > > > > > > ServletStubImpl.java:518) > > > > > > > > at > > > > weblogic.servlet.internal.ServletStubImpl.invokeServlet ( > > > > > > > > ServletStubImpl.java:362) > > > > > > > > at > > > > weblogic.servlet.internal.ServletStubImpl.invokeServlet( > > > > > > > > ServletStubImpl.java:305) > > > > > > > > at > > > > > > > > > > weblogic.servlet.internal.WebAppServletContext$ServletInvoca > > > > > > > > ti > > > > > > > > onAction.run( > > > > > > > > WebAppServletContext.java :6350) > > > > > > > > at > > > > weblogic.security.acl.internal.AuthenticatedSubject.doAs( > > > > > > > > AuthenticatedSubject.java:317) > > > > > > > > at > > > > > > > > > > > > > > > > > > > > weblogic.security.service.SecurityManager.runAs(SecurityManager.java > > > > > > > > :118) > > > > > > > > at > > > > > > weblogic.servlet.internal.WebAppServletContext.invokeServlet > > > > > > > > ( > > > > > > > > WebAppServletContext.java:3635) > > > > > > > > at > > weblogic.servlet.internal.ServletRequestImpl.execute( > > > > > > > > ServletRequestImpl.java:2585) > > > > > > > > at > > > > > > weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197) > > > > > > > > at weblogic.kernel.ExecuteThread.run > > > > > > > > (ExecuteThread.java:170) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > > > > - > > > > > > > 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] > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > 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] > >
