…on is thrown while trying to send the message or flush the connection. Leaving _activeMessage set causes WriteMessageInsideLock to always return a "NoConnectionAvailable" error indefinitely

Tidying this up so the diff/fix in #1374 is easier to analyze.

This was referenced

NickCraver linked an issue

that may be closed by this pull request

This was referenced

NickCraver linked an issue

that may be closed by this pull request

NickCraver linked an issue

that may be closed by this pull request

NickCraver linked an issue

that may be closed by this pull request

This was referenced

NickCraver linked an issue

that may be closed by this pull request

NickCraver linked an issue

that may be closed by this pull request

NickCraver linked an issue

that may be closed by this pull request

NickCraver linked an issue

that may be closed by this pull request

This was referenced

NickCraver linked an issue

that may be closed by this pull request

This was referenced

edgarrs pushed a commit to microsoft/BuildXL that referenced this pull request

This PR updates `Redis.StackExchange` library to version 2.1.30 to include a fix that supposedly solves the problem with the inability of a process to connect to Redis instance.

This is the PR that this version includes: StackExchange/StackExchange.Redis#1374

We do have many cases when the process fails to connect to on Redis instance and after the service restart it immediately (within seconds) successfully connects to it.

Related work items: #1697377