velocity-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SebastianWagner (JIRA)" <>
Subject [jira] Commented: (VELOCITY-621) Update to SLF4J or workaround?
Date Tue, 07 Oct 2008 16:14:44 GMT


SebastianWagner commented on VELOCITY-621:

At the moment you get errors like:

DEBUG] [pool-4-thread-16] org.apache.velocity - CommonsLogLogChute name is 'org.apache.velocity'
[DEBUG] [pool-4-thread-16] org.apache.velocity - Starting Apache Velocity v1.6-dev (compiled:
2007-04-04 11:16:14)
[DEBUG] [pool-4-thread-16] org.apache.velocity - Default Properties File: org/apache/velocity/runtime/defaults/
[DEBUG] [pool-4-thread-16] org.apache.velocity - Trying to use logger class org.apache.velocity.runtime.log.AvalonLogChute
[DEBUG] [pool-4-thread-16] org.apache.velocity - Target log system for org.apache.velocity.runtime.log.AvalonLogChute
is not available (java.lang.NoClassDefFoundError: org/apache/log/format/Formatter).  Falling
back to next log system...
[DEBUG] [pool-4-thread-16] org.apache.velocity - Trying to use logger class org.apache.velocity.runtime.log.Log4JLogChute
[DEBUG] [pool-4-thread-16] org.apache.velocity - Target log system for org.apache.velocity.runtime.log.Log4JLogChute
is not available (java.lang.NoClassDefFoundError: org/apache/log4j/Appender).  Falling back
to next log system...
[DEBUG] [pool-4-thread-16] org.apache.velocity - Trying to use logger class org.apache.velocity.runtime.log.JdkLogChute
[INFO] [pool-4-thread-16] org.apache.velocity - Failed to initialize an instance of org.apache.velocity.runtime.log.JdkLogChute
with the current runtime configuration.
java.lang.IllegalArgumentException: Bad level "WARN"
	at java.util.logging.Level.parse(
	at org.apache.velocity.runtime.log.JdkLogChute.init(
	at org.apache.velocity.runtime.log.LogManager.createLogChute(
	at org.apache.velocity.runtime.log.LogManager.updateLog(
	at org.apache.velocity.runtime.RuntimeInstance.initializeLog(
	at org.apache.velocity.runtime.RuntimeInstance.init(
	at org.apache.velocity.runtime.RuntimeInstance.init(
	at org.apache.velocity.runtime.RuntimeSingleton.init(
	at<init>(Unknown Source)
	at<init>(Unknown Source)
	at Source)
	at Source)
	at Source)
	at Source)
	at Source)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
	at java.lang.reflect.Method.invoke(
	at org.red5.server.service.ServiceInvoker.invoke(
	at org.red5.server.service.ServiceInvoker.invoke(
	at org.apache.mina.filter.executor.ExecutorFilter.processEvent(
	at org.apache.mina.filter.executor.ExecutorFilter$
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
	at java.util.concurrent.ThreadPoolExecutor$

> Update to SLF4J or workaround?
> ------------------------------
>                 Key: VELOCITY-621
>                 URL:
>             Project: Velocity
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: 1.4, 1.5
>            Reporter: SebastianWagner
> I know that it has been discussed one year ago in  VELOCITY-392
> but there is need for at least a workaround for people who are forced to use slf4j.
> For example other frameworks did already switch like Hibernate.
> So there is now definitely need for something to enable Velocity to run without errors
in a environment with log4j-over-slf4j. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message