I've had similar issues. Was resolved by adding application classpath to startup script before JBOSS classpath. Ultimately we decided to just use JBOSS'S /server/default/all/conf/ ... Xml configuration for logging. On 5/3/06 11:15 AM, "robert burrell donkin" wrote: > On Wed, 2006-05-03 at 11:25 +0300, Amit Jha wrote: >> I had the same problem when I included commons-logging.jar and log4j.jar in >> WEB-INF/lib >> Once I removed it from there everything was fine. >> It seems it has conflict with what Jboss log4j has already. > > if that doesn't work then please try JCL 1.1 RC10 > http://people.apache.org/~rdonkin/commons-logging. > > - robert > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: commons-user-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org