The moose likes BEA/Weblogic and the fly likes 'weblogic.logging.commons.LogFactoryImpl' cannot be converted to 'org.apache.commons.logging.LogFact Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Products » BEA/Weblogic
Bookmark " Watch " New topic

'weblogic.logging.commons.LogFactoryImpl' cannot be converted to 'org.apache.commons.logging.LogFact

subbarao kollipara

Joined: Oct 25, 2011
Posts: 1

I am calling axis2 webservice from the weblogic portal, after including the code related to axis2 client, i have the following exception.

The application has specified that a custom LogFactory implementation should be used but Class 'weblogic.logging.commons.LogFactoryImpl' cannot be converted to 'org.apache.commons.logging.LogFactory'. The conflict is caused by the presence of multiple LogFactory classes in incompatible classloaders. Background can be found in http://commons.apache.org/logging/tech.html. If you have not explicitly specified a custom LogFactory then it is likely that the container has set one without your knowledge. In this case, consider using the commons-logging-adapters.jar file or specifying the standard LogFactory from the command line. Help can be found @http://commons.apache.org/logging/troubleshooting.html.

I added following property in the weblogic.xml file

and i also tried by adding the commons-logging.jar and wlcommons-logging.jar file in WEB-INF\lib folder of the application
as well as into they domain\lib folder. Still i am facing the issues.

Please Help me to resolve this issue.
It is sorta covered in the JavaRanch Style Guide.
subject: 'weblogic.logging.commons.LogFactoryImpl' cannot be converted to 'org.apache.commons.logging.LogFact
Similar Threads
WebLogic 9.2 clustering problem
Tomcat 6.0.35 hangs during startup
OpenSAML runtime exception java.lang.NoClassDefFoundError: org/apache/xml/security/Init
The jar synchronization issue seems to be out of hand.
apache logging in websphere...