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

Fix log level on error with @TransactionalEventListener #30776

Merged
merged 1 commit into from
Jun 30, 2023

Conversation

KSH-code
Copy link
Contributor

@KSH-code KSH-code commented Jun 30, 2023

Synchronous methods with @TransactionalEventListener logs in debug level.
However, most production logs are filtered by error level. Thus most developers cannot detect @TransactionalEventListener method throws error whether or not.

It was changed from 95110d8. I think this changed an error because it is not related to commit message.

ref: #17162

@pivotal-cla
Copy link

@KSH-code Please sign the Contributor License Agreement!

Click here to manually synchronize the status of this Pull Request.

See the FAQ for frequently asked questions.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Jun 30, 2023
@pivotal-cla
Copy link

@KSH-code Thank you for signing the Contributor License Agreement!

@KSH-code KSH-code changed the title TransactionalEventListener method log level to error level Change debug log level into error in @TransactionalEventListener Jun 30, 2023
@KSH-code KSH-code changed the title Change debug log level into error in @TransactionalEventListener Fix log level on error with @TransactionalEventListener Jun 30, 2023
@jhoeller jhoeller self-assigned this Jun 30, 2023
@jhoeller jhoeller added in: data Issues in data modules (jdbc, orm, oxm, tx) type: regression A bug that is also a regression and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Jun 30, 2023
@jhoeller jhoeller added this to the 6.0.11 milestone Jun 30, 2023
@jhoeller jhoeller added for: backport-to-5.3.x status: backported An issue that has been backported to maintenance branches and removed for: backport-to-5.3.x labels Jun 30, 2023
@jhoeller
Copy link
Contributor

Good point, it is not clear why that log level got downgraded to debug, this might have been an accident indeed. While regular transaction synchronizations are not meant to throw an exception there to begin with, this may certainly happen for transactional event processing and should be visible there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) status: backported An issue that has been backported to maintenance branches type: regression A bug that is also a regression
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants