none
Service bus errored unexpectedly and repeatedly with a timeout exception

    Question

  • We've experienced some interesting partial outages because some messages randomly get their timeouts. This occurred over ~ 10 minutes today, with 2 service bus instances seemingly having trouble.

    Involved tracking ids are:

    57bc4e03-ea0b-4092-8410-65d8edc55ce7

    a110fdac-8599-4186-b1d5-eca53322597

    More information about the error (it resulted in an error in the underlying framework) can be found at https://github.com/Particular/NServiceBus.AzureServiceBus/issues/273#issuecomment-279125904 where discussion took place today about this issue.

    Any help would be appreciated!

    Saturday, February 11, 2017 3:45 PM

Answers

  • Occasional transient errors, even episodes of errors, are to be expected at times, especially also on Service Bus Standard namespaces. If the ownership of a queue changes inside the system or system update rolls through, timeouts and errors can occur on those entities aswe aim to protect consistency and favor transient errors over any risk of data loss. 

    I assume the error does not persist right now. What was the ratio of errors to succeeded operations?

    • Marked as answer by janpieterz Wednesday, March 01, 2017 12:10 PM
    Monday, February 13, 2017 10:13 AM

All replies

  • Occasional transient errors, even episodes of errors, are to be expected at times, especially also on Service Bus Standard namespaces. If the ownership of a queue changes inside the system or system update rolls through, timeouts and errors can occur on those entities aswe aim to protect consistency and favor transient errors over any risk of data loss. 

    I assume the error does not persist right now. What was the ratio of errors to succeeded operations?

    • Marked as answer by janpieterz Wednesday, March 01, 2017 12:10 PM
    Monday, February 13, 2017 10:13 AM
  • It was negligible, lasted for a while but wasn't too serious but had because of this a rollover effect.

    Thanks for your response!

    Wednesday, March 01, 2017 12:10 PM