-
Notifications
You must be signed in to change notification settings - Fork 2k
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] Continuous logs from com.azure.core.amqp.implementation.RequestResponseChannel as part of the event hub messaging implementation #31487
Comments
@conniey could you please follow up |
We've made several reliability changes in 5.14.0 that reduce the number of attempts. Does it still reproduce on the latest version? |
Hi @conniey , No, I don't see a considerable difference in the continuous logs with 5.14.0 2022-10-21 10:55:09 INFO RequestResponseChannel:$management:429 - namespace[MF_db5a6b_1666329907985] entityPath[$management]: Setting next AMQP channel. |
If I understand correctly, the processing doesn't stop, but the issue is seeing a lot of logs. Unfortunately, this is our current behaviour due to the asynchronous state of each AMQP component. But we do have a github issue to reduce the number of logs #20836 What is the expression in log4j2 you're using to exclude the logs? We have a few examples linked in our TROUBLESHOOTING.md |
This will be fixed as part of #33378 |
Continuous logs from com.azure.core.amqp.implementation.RequestResponseChannel
Using EventProcessorClient for streaming Eventhub.
Have also tried to exclude the logs of the library with log4j2 but logs continue to flow!
The text was updated successfully, but these errors were encountered: