-
Notifications
You must be signed in to change notification settings - Fork 44
Event hub client - Unauthorized access due to "InvalidOperationError: $cbs node has already been opened" when renewing token #186
Comments
@MatejSkrbis What majority of your logs is showing is the AMQP link throwing the Unauthorized access error and the subsequent closing of the link. This is happening for 3 of the receiver links. Before that, there is an error when trying to renew the token (see below), because there is already a request in flight to do the same.
Can you provide logs that include the above as well as what happened before that? |
I had DEBUG set to "azure:event-hubs:error,azure-amqp-common:error,rhea-promise:error,rhea:events,rhea:frames,rhea:io,rhea:flow". These are logs 10 minutes before Unauthorized error:
|
Today I am receiving those Unauthorized access errors like crazy. I got multiple event hubs and multiple event hub namespaces used by different server instances. I got them simultaneously with different servers using different event hub namespaces (probably located in same data center). Might this error be connected to some underlying infrastructure problems? I can provide more logs from today if needed, |
Thanks for the logs @MatejSkrbis It looks there are a series of The The
That could very much be possible. I'll try and reach out to folks and Event Hubs to see if they can help. |
@MatejSkrbis From your logs in
We do use a lock on the cbsSession to avoid such scenarios, I will continue to look into how this could happen. Meanwhile, a few follow up questions for you which can help shed more light on your exact scenario.
|
Here are the logs for connection-2 of what was happening before logs I posted:
|
Here are the logs when reading was started from event-hub4
|
Thanks @MatejSkrbis, that gives us some leads. We will get back to you soon |
Thanks a lot for your patience @MatejSkrbis, we were able to piece together the below summary
In conclusion, for the first issue, you will need the updated version of Regarding the second issue, we are working on a fix and plan to ship an update to |
@MatejSkrbis Thanks for your patience. We have just released a new version 2.0.0 for the Event Hubs library which includes the fix for the 2 errors being discussed in this issue.
For details on what the underlying problem was, please see the changelog. Please keep in mind that there is a major version update in this release. This is because of a few breaking changes for which you may have to react to and make some changes in your code. Please see the changelog for the list of breaking changes and bug fixes. |
From #174 (comment) by @MatejSkrbis
The text was updated successfully, but these errors were encountered: