search

Azure / azure-service-bus-java

☁️ Java client library for Azure Service Bus
https://azure.microsoft.com/services/service-bus
MIT License
60 stars 59 forks source link

Wrong logging level using the servicebus #368

Closed clacmago closed 5 years ago

clacmago commented 5 years ago

Describe the bug We have discovered that azure servicebus is writing a large number of error entries to our application logs, since we are permanently sending and receiving from azure.

We examined a number of these entries and we believe they should be categorised as INFO level logging rather than ERROR level logging.

Expected behavior We expected the INFO logging to be reported as such in the Java console and in the application. All efforts intended to switch off or to change the logging level from our side using a log4j.properties configuration brought no result.

Observed behavior [pool-2-thread-3] INFO com.microsoft.azure.servicebus.primitives.MessagingFactory - Closing messaging factory [pool-2-thread-3] INFO com.microsoft.azure.servicebus.primitives.MessagingFactory - Closing CBS link [pool-2-thread-3] INFO com.microsoft.azure.servicebus.primitives.RequestResponseLink - Closing requestresponselink to $cbs by closing both internal sender and receiver links. [ReactorThread62591d73-0f5e-4355-ace7-11223e9fddcd] INFO com.microsoft.azure.servicebus.primitives.RequestResponseLink - Closed internal send link of requestresponselink to $cbs [ReactorThread62591d73-0f5e-4355-ace7-11223e9fddcd] INFO com.microsoft.azure.servicebus.primitives.RequestResponseLink - Closed internal receive link of requestresponselink to $cbs

Bildschirmfoto 2019-06-04 um 14 48 25

Environment (please complete the following information):

clacmago commented 5 years ago

Binding with the appropriate logging framework using slf4j-log4j12-1.7.26.jar was the solution. The former Binding with slf4j-simple-1.7.26.jar produced the system.err logs for our case.