| 'org.eclipse.hyades.logging.commons.FileLoggerFactory' cannot be converted to 'org.apache.commons.lo [message #119215] |
Sun, 09 December 2007 08:19 |
Eclipse User |
|
|
|
Originally posted by: nospam_st.gmx.net
Hi,
I tried to profile a Grails application. However when I try to run the
application in profiling mode I am getting the exception below. Grails
uses commons-logging and this exception looks like a classloader issue
between some TPTP components and grails. The FAQ of commons-logging also
lists such an exception
http://commons.apache.org/logging/commons-logging-1.1/troubl eshooting.html#The_Incompatible_LogFactory_Issue
and provides a workaround, however it does not seem to work.
Any thoughts are appreciated.
Thanks,
Seb
------------------------------------------------------------ -----------------
Exception in thread "main" java.lang.ExceptionInInitializerError
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at
org.codehaus.groovy.grails.cli.GrailsScriptRunner.class$(Gra ilsScriptRunner.groovy)
at
org.codehaus.groovy.grails.cli.GrailsScriptRunner.<clinit>(GrailsScriptRunner.groovy:35)
<snip/>
at grails.util.GrailsMain.main(GrailsMain.groovy)
Caused by: org.apache.commons.logging.LogConfigurationException: The
chosen LogFactory implementation does not extend LogFactory. Please
check your configuration. (Caused by java.lang.ClassCastException: The
application has specified that a custom LogFactory implementation should
be used but Class 'org.eclipse.hyades.logging.commons.FileLoggerFactory'
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://jakarta.apache.org/commons/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://jakarta.apache.org/commons/logging/troubleshooting.h tml.)
at
org.apache.commons.logging.LogFactory.createFactory(LogFacto ry.java:1200)
at org.apache.commons.logging.LogFactory$2.run(LogFactory.java: 994)
at java.security.AccessController.doPrivileged(Native Method)
at org.apache.commons.logging.LogFactory.newFactory(LogFactory. java:991)
at org.apache.commons.logging.LogFactory.getFactory(LogFactory. java:572)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java :645)
at
org.springframework.core.io.support.PathMatchingResourcePatt ernResolver. <clinit>(PathMatchingResourcePatternResolver.java:163)
... 43 more
Caused by: java.lang.ClassCastException: The application has specified
that a custom LogFactory implementation should be used but Class
'org.eclipse.hyades.logging.commons.FileLoggerFactory' 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://jakarta.apache.org/commons/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://jakarta.apache.org/commons/logging/troubleshooting.h tml.
at
org.apache.commons.logging.LogFactory.createFactory(LogFacto ry.java:1149)
... 49 more
|
|
|
Powered by
FUDForum. Page generated in 0.07210 seconds
Home