commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 37954] New: - provide better error message than "No suitable Log implementation"
Date Sun, 18 Dec 2005 16:41:27 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37954>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37954

           Summary: provide better error message than "No suitable Log
                    implementation"
           Product: Commons
           Version: unspecified
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: Logging
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: hauser@acm.org


when trying to do a totally different ant task, I got with debug the following
exception

...\build.xml:3125: java.lang.ExceptionInInitial
izerError
        at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:114)
        at org.apache.tools.ant.Task.perform(Task.java:365)
        at org.apache.tools.ant.Target.execute(Target.java:356)
        at org.apache.tools.ant.Target.performTasks(Target.java:384)
        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1236)
        at org.apache.tools.ant.Project.executeTarget(Project.java:1205)
        at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1088)
        at org.apache.tools.ant.Main.runBuild(Main.java:676)
        at org.apache.tools.ant.Main.startAnt(Main.java:195)
        at org.apache.tools.ant.launch.Launcher.run(Launcher.java:265)
        at org.apache.tools.ant.launch.Launcher.main(Launcher.java:87)
Caused by: java.lang.ExceptionInInitializerError
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:242)
        at org.apache.tools.ant.taskdefs.Definer.addDefinition(Definer.java:551)
        at org.apache.tools.ant.taskdefs.Definer.execute(Definer.java:221)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
        at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:104)
        ... 11 more
Caused by: org.apache.commons.logging.LogConfigurationException: No suitable Log
implementation
        at
org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:748)
        at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:556)
        at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:307)
        at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:281)
        at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:560)
        at org.apache.jasper.JspC.<clinit>(JspC.java:90)
        ... 20 more
--- Nested Exception ---
java.lang.ExceptionInInitializerError
        at java.lang.Class.forName0(Native Method)
        at java.lang.Class.forName(Class.java:242)
        at org.apache.tools.ant.taskdefs.Definer.addDefinition(Definer.java:551)
        at org.apache.tools.ant.taskdefs.Definer.execute(Definer.java:221)
        at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
        at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
        at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:585)
        at
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:104)
        at org.apache.tools.ant.Task.perform(Task.java:365)
        at org.apache.tools.ant.Target.execute(Target.java:356)
        at org.apache.tools.ant.Target.performTasks(Target.java:384)
        at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1236)
        at org.apache.tools.ant.Project.executeTarget(Project.java:1205)
        at
org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
        at org.apache.tools.ant.Project.executeTargets(Project.java:1088)
        at org.apache.tools.ant.Main.runBuild(Main.java:676)
        at org.apache.tools.ant.Main.startAnt(Main.java:195)
        at org.apache.tools.ant.launch.Launcher.run(Launcher.java:265)
        at org.apache.tools.ant.launch.Launcher.main(Launcher.java:87)
Caused by: org.apache.commons.logging.LogConfigurationException: No suitable Log
implementation
        at
org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:748)
        at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:556)
        at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:307)
        at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:281)
        at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:560)
        at org.apache.jasper.JspC.<clinit>(JspC.java:90)
        ... 20 more

Total time: 13 secondsClass org.apache.commons.logging.impl.LogFactoryImpl
loaded from ant loader (parentFirst)
Class java.lang.ExceptionInInitializerError loaded from parent loader (parentFirst)



looking at the CVS head, there might be some relief:

"User-specified log class " + specifiedLogClassName
                        + " cannot be found or is not useable."

but still, it would be really helpful to know what was missing from an admin
point of view, so on top of the particular class name, it would be very useful,
to get a hint at 
1) which jar (log4j.jar) that "specifiedLogClassName" most likely is included in? 
2) Or whether the config file was missing (log4j.properties?) and in 
3) which directories/jar files it was searched for...
4) and what "logCategory" was being aimed for...

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message