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

GH-5000: Tone down WARN log output for frequent, non-critical events #5006

Merged
merged 1 commit into from
Jun 17, 2024

Conversation

fkleedorfer
Copy link
Contributor

@fkleedorfer fkleedorfer commented Jun 1, 2024

GitHub issue resolved: #5000

Briefly describe the changes proposed in this PR:

Reduces loglevel for two very frequent, not-so-serious situations


PR Author Checklist (see the contributor guidelines for more details):

  • my pull request is self-contained
  • [~] I've added tests for the changes I made
  • I've applied code formatting (you can use mvn process-resources to format from the command line)
  • I've squashed my commits where necessary
  • every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

@fkleedorfer fkleedorfer changed the title GH-4997: Tone down WARN log output for frequent, non-critical events GH-5000: Tone down WARN log output for frequent, non-critical events Jun 1, 2024
@@ -95,7 +95,7 @@ public void closeConnection() {
} finally {
try {
if (con != null && con.isActive()) {
logger.warn(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you explain why this should be debug instead of warn? Seems like a fairly critical issue with the users code.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On second thought, I agree with you.

I wanted to reduce the loglevel because I've seen this a lot in my logs without it being of any use, as there were other log messages generated in the same transaction by the problem eventually also leading to this. However, It's just one line, and it is, as you say, pretty serious (the explicit commit or rollback must have failed somehow), so let's leave it in. It might actually be worth digging into the cases in which the message shows up.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

reverted that change.

@hmottestad hmottestad merged commit 1749af8 into eclipse-rdf4j:main Jun 17, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

rdf4j-spring: Suppress logging of exceptions if they are thrown on.
2 participants