Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot update log level of SimpleBrokerMessageHandler using actuator #25082

Closed
nickcaballero-mm opened this issue May 14, 2020 · 1 comment
Closed
Labels
in: messaging Issues in messaging modules (jms, messaging) status: duplicate A duplicate of another issue

Comments

@nickcaballero-mm
Copy link

The log level used by SimpleBrokerMessageHandler cannot be updated via actuator. When debugging, it seems that it uses a org.springframework.core.log.CompositeLog that determines the log levels when creating the instance. This means that the only way to increase the logging level is to stop the server and update the configuration.

As a workaround, we can start the server with a higher logging level and then reduce it using actuator once server has started.

Affects: spring-messaging 5.2.5.RELEASE

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label May 14, 2020
@rstoyanchev rstoyanchev added the in: messaging Issues in messaging modules (jms, messaging) label Nov 12, 2021
@jhoeller
Copy link
Contributor

This should be addressed through #28477 as of 5.3.21 now.

@jhoeller jhoeller added status: duplicate A duplicate of another issue and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Dec 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: messaging Issues in messaging modules (jms, messaging) status: duplicate A duplicate of another issue
Projects
None yet
Development

No branches or pull requests

4 participants