[QUERY] How to catch the networking error while use the azure-stream-binder SDK

[yunbozhang-msft]

Question
We are using SDK: com.azure.spring:spring-cloud-azure-stream-binder-eventhubs
Team, do you know how to catch the networking error while use this SDK?

When we process the message in the consume method, we have successfully received the message, but if there is a problem with the network before that, we do not consume the message, or it causes a retry. Do you know how to handle this network anomaly?

Why is this not a Bug or a feature Request?
I do not know how to catch networking error.

Setup (please complete the following information if applicable):

• OS: [e.g. iOS] NA
• IDE: [e.g. IntelliJ] NA
• Library/Libraries: [e.g. com.azure:azure-core:1.16.0 (groupId:artifactId:version)] com.azure.spring:spring-cloud-azure-stream-binder-eventhubs

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

• Query Added
• Setup information Added

[github-actions]

@chenrujun @moarychan @Netyyyy @saragluna

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[saragluna]

I any error is thrown from this consumer, you could use this approach to listen to the error channel, https://github.com/Azure-Samples/azure-spring-boot-samples/blob/17291f4816b2cf833bd6dbadbde48eb652bfb8c9/eventhubs/spring-cloud-azure-stream-binder-eventhubs/eventhubs-binder/src/main/java/com/azure/spring/sample/eventhubs/binder/EventHubBinderApplication.java#L25-L36.

Or you could refer to this doc https://docs.spring.io/spring-cloud-stream/reference/spring-cloud-stream/overview-error-handling.html for Spring Cloud Stream error handling.

[yunbozhang-msft]

Thank you @saragluna

[github-actions]

Hi @yunbozhang-msft. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.

[github-actions]

Hi @yunbozhang-msft, since you haven’t asked that we /unresolve the issue, we’ll close this out. If you believe further discussion is needed, please add a comment /unresolve to reopen the issue.