A very small number of messages that are being processed (0.04%) sometimes result in an exception that triggers the circuit breaker. This exception is benign, and we are comfortable with not having the circuit breaker kick in. There is currently no known way or plan to eliminate the root cause of this exception being raised, as it is thrown by the ASB SDK. The issue with the circuit breaker being armed is that it throttles message processing which causes more problems.
Please note that this exception has been around for several years and never caused any issues while we were on NSB version 7.8.0 and prior. It is only after upgrading to version 8.2.2 that the circuit breaker started behaving this way when encountering this exception.
Is it possible to override/ignore this critical error (or somehow not treat it as one)? If not, is it possible to disable the circuit breaker in its entirety? I appreciate that this is not advisable, but we have never relied on it in the past and have our own custom recoverability.