You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Claus Ibsen (Jira)" <ji...@apache.org> on 2021/06/10 11:11:00 UTC

[jira] [Updated] (CAMEL-16705) camel-spring-boot - Changing LoggingLevel for Camel Log at runtime

     [ https://issues.apache.org/jira/browse/CAMEL-16705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-16705:
--------------------------------
    Summary: camel-spring-boot - Changing LoggingLevel for Camel Log at runtime  (was: Changing LoggingLevel for Camel Log at runtime)

> camel-spring-boot - Changing LoggingLevel for Camel Log at runtime
> ------------------------------------------------------------------
>
>                 Key: CAMEL-16705
>                 URL: https://issues.apache.org/jira/browse/CAMEL-16705
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 3.6.0, 3.7.0, 3.8.0, 3.9.0, 3.10.0
>            Reporter: Christian Rossius
>            Priority: Minor
>              Labels: log, log-level, logging
>
> The default LogLevel is INFO. When i want to change this by spring boot actuator (JMX) to ERROR or WARN it works, but when i want to change it to DEBUG or TRACE it don't.
> If I set the LogLevel at the beginning to TRACE, I can change it down to any other Level manually.
> So decreasing works, but increasing the LogLevel dont.
> It only applied to logging in Camel Routes. It works great on any other Logging.
> In Version 3.5.0 and below it worked. All versions after that don't work anymore.
> It is also descibed here [https://stackoverflow.com/questions/66357203/changing-camel-log-level-at-runtime-using-spring-boot-actuator|Stackoverflow]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)