On Tue, 2006-01-31 at 17:36 -0600, Srilatha Alase wrote: > Hi Robert, > Thank you for your input.. > > When I changed the commons-logging.properties to have the following entry:- > org.apache.commons.logging.Log=org.apache.commons.logging.impl.Log4jLogger > > Now I'm getting an error on startup > > Caused by: org.apache.commons.logging.LogConfigurationException: > org.apache.commons.logging.LogConfigurationException: > java.lang.ClassNotFoundException: org.apache.commons.logging.impl.Log4jLogger > ...
the stack's pretty clear: org.apache.commons.logging.impl.Log4jLogger cannot be loaded. the open question is why it can't be loaded. > I do have commons-logging-1.0.4.jar in the server classpath,also added a > custom classloader in WSAD 5.1 > to use the commons-logging-1.0.4.jar. the most likely explanation is that there are multiple JCL jars in your classpath including an API jar. debugging a complex classloader configuration (such as is found in modern J2EE containers) with multiple JCL jars requires specialist knowledge and expertise. so, the easiest approach is usually just to remove all JCL jars (so the application fails with a java.lang.ClassNotFoundException for either org.apache.commons.logging.Log or org.apache.commons.logging.LogFactory). then add one full jar (commons-logging-1.0.4.jar) back and see if it works. alternatively, we've been working hard on JCL 1.1. this has a lot of improvements including better diagnostics. a release candidate is available from http://people.apache.org/~rdonkin/commons-logging/. please read the release notes carefully. remove all old jar's (by following the process outlined above) and then try the new jar instead. if it doesn't work, try running with the system property org.apache.commons.logging.diagnostics.dest=STDERR (or STDOUT). - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
