Claus Ibsen-2 wrote
> The log uses the route name as the logger name by default.
>
> You can try to specify a logger name to use with the 3 args version
> public Type log(LoggingLevel loggingLevel, String logName, String
> message) {
I specified the three args version with the following:
from("jms:queue:CAMEL_IN").to("multiplier").*log(LoggingLevel.ERROR,
"com.test.Foo", "this is a test ${body}")*.to("jms:queue:CAMEL_OUT");
Still not seeing the log statement from the route however the following logs
are being produced:
2013-12-04 20:40:36 DEBUG
org.apache.camel.component.jms.DefaultJmsMessageListenerContainer:313 -
Received message of type [class
org.apache.activemq.command.ActiveMQTextMessage] from consumer
[PooledMessageConsumer { ActiveMQMessageConsumer {
value=ID:robs-MacBook-Pro.local-61189-1386207612100-1:2:2:1, started=true }
}] of session [PooledSession { ActiveMQSession
{id=ID:robs-MacBook-Pro.local-61189-1386207612100-1:2:2,started=true} }]
2013-12-04 20:40:36 DEBUG
org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate:464 -
Executing callback on JMS Session: PooledSession { ActiveMQSession
{id=ID:robs-MacBook-Pro.local-61189-1386207612100-1:2:2,started=true} }
Claus Ibsen-2 wrote
> And do you run your Camel app is some container or does this happen
> also from an unit test or running standalone etc?
I have been using the maven plugin "mvn camel:run"
--
View this message in context:
http://camel.465427.n5.nabble.com/DSL-Logging-not-outputting-to-the-logs-tp5744093p5744340.html
Sent from the Camel - Users mailing list archive at Nabble.com.
