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.

Sign up for GitHub

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

Jump to bottom

[BUG] Service bus sender client: connection errors in logs #39575

Closed
ViacheslavPetriaievEBT opened this issue Apr 5, 2024 · 6 comments · Fixed by #39904
Closed

[BUG] Service bus sender client: connection errors in logs #39575

ViacheslavPetriaievEBT opened this issue Apr 5, 2024 · 6 comments · Fixed by #39904
Assignees
@lmolkova
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Bus

Comments

@ViacheslavPetriaievEBT
Copy link

ViacheslavPetriaievEBT commented Apr 5, 2024 •
edited

Describe the bug
The sender client works, and messages are sent successfully to a service bus. But from time to time, there are several types of errors appear in the logs:

  • com.azure.core.amqp.exception.AmqpException: Connection reset, errorContext[NAMESPACE: *****.servicebus.windows.net. ERROR CONTEXT: N/A]
  • com.azure.core.amqp.exception.AmqpException: Connection timed out: getsockopt, errorContext[NAMESPACE: *****.servicebus.windows.net. ERROR CONTEXT: N/A]
  • com.azure.core.amqp.exception.AmqpException: connection aborted, errorContext[NAMESPACE: *****.servicebus.windows.net. ERROR CONTEXT: N/A]

These errors have no influence on the message-sending process, all messages are sent successfully. But in Application insights -> Logs messages have severity level = 3 (Error), which leads to false-positive error notifications.

Exception or Stack Trace

reactor.core.Exceptions$ErrorCallbackNotImplemented: com.azure.core.amqp.exception.AmqpException: connection aborted, errorContext[NAMESPACE: ***********.servicebus.windows.net. ERROR CONTEXT: N/A]
Caused by: com.azure.core.amqp.exception.AmqpException: connection aborted, errorContext[NAMESPACE *********.servicebus.windows.net. ERROR CONTEXT: N/A]
at com.azure.core.amqp.implementation.ExceptionUtil.toException(ExceptionUtil.java:85)
at com.azure.core.amqp.implementation.handler.ConnectionHandler.notifyErrorContext(ConnectionHandler.java:362)
at com.azure.core.amqp.implementation.handler.ConnectionHandler.onTransportError(ConnectionHandler.java:259)
at org.apache.qpid.proton.engine.BaseHandler.handle(BaseHandler.java:191)
at org.apache.qpid.proton.engine.impl.EventImpl.dispatch(EventImpl.java:108)
at org.apache.qpid.proton.reactor.impl.ReactorImpl.dispatch(ReactorImpl.java:324)
at org.apache.qpid.proton.reactor.impl.ReactorImpl.process(ReactorImpl.java:291)
at com.azure.core.amqp.implementation.ReactorExecutor.run(ReactorExecutor.java:91)
at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:68)
at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:28)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:840)

Code Snippet

spring:
  cloud:
    azure:
      servicebus:
        namespace: ${service-bus-namespace}
        producer:
          entity-name: ${service-bus-queue-name}
          entity-type: QUEUE


ServiceBusSenderClient client; - injected client
client.sendMessage(message);

Setup (please complete the following information):

  • OS: Windows
  • Library: com.azure.spring:spring-cloud-azure-starter-servicebus:5.10.0
  • Java version: 21
  • App Server/Environment: Azure Function, standalone app running
  • Frameworks: Spring Boot
@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Apr 5, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Apr 5, 2024

@anuchandy @conniey @lmolkova

@github-actions github-actions bot added needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Bus labels Apr 5, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Apr 5, 2024

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

@lmolkova
Copy link
Member

lmolkova commented Apr 5, 2024

@ViacheslavPetriaievEBT transient network issues are expected and based on your description are retried and don't result in visible impact.
Is the ask here to reduce the severity to warning?

Would you expect error severity if ServiceBus SDK hits unrecoverable issue (either retries are exhausted or issue is not transient)?

@ViacheslavPetriaievEBT
Copy link
Author

@lmolkova
Yes, that's correct:

  • warning - for recoverable issues
  • error - for unrecoverable issues

@lmolkova lmolkova mentioned this issue Apr 24, 2024
Merged
@lmolkova
Copy link
Member

lmolkova commented Apr 24, 2024 •
edited

@ViacheslavPetriaievEBT thank you for the confirmation!
Do you have an examples of the messages coming from ServiceBus SDK and logger/class name?

I'm trying to change levels in the #39904, but the stack trace and error messages describe the exception and not the place where it's logged. Having a few examples of specific messages/logger names would really help to apply fixes in the places which affect your application.

Thanks!

@ViacheslavPetriaievEBT
Copy link
Author

@lmolkova
I've found only the following information:

  • Logger Message: Operator called default onErrorDropped
  • LoggerName: reactor.core.publisher.Operators
  • SourceType: Logger

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lmolkova lmolkova

Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Bus
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Messaging (Event Hubs, Service Bus) logging improvements lmolkova/azure-sdk-for-java
2 participants
@lmolkova @ViacheslavPetriaievEBT