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

[Bug] Stop hijacking logging of Netty #8030

Open
3 tasks done
lizhanhui opened this issue Apr 17, 2024 · 0 comments · May be fixed by #8031
Open
3 tasks done

[Bug] Stop hijacking logging of Netty #8030

lizhanhui opened this issue Apr 17, 2024 · 0 comments · May be fixed by #8031

Comments

@lizhanhui
Copy link
Contributor

Before Creating the Bug Report

  • I found a bug, not just asking a question, which should be created in GitHub Discussions.

  • I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

  • I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

N/A

RocketMQ version

ALL

JDK Version

N/A

Describe the Bug

Remoting module hijacks and sets Netty logging level to ERROR by default and this does not make sense. Configuration to netty logging should be up to application developers.

Steps to Reproduce

Unable to log netty disagnosis logging

What Did You Expect to See?

Application developers shall be able to configure netty logging

What Did You See Instead?

Remoting module hijacks and setting netty logging level to error in a static block.

Additional Context

No response

lizhanhui added a commit to lizhanhui/rocketmq that referenced this issue Apr 17, 2024
Signed-off-by: Li Zhanhui <lizhanhui@gmail.com>
@lizhanhui lizhanhui linked a pull request Apr 17, 2024 that will close this issue
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 a pull request may close this issue.

1 participant