search

Azure / azure-sdk-for-js

This repository is for active development of the Azure SDK for JavaScript (NodeJS & Browser). For consumers of the SDK we recommend visiting our public developer docs at https://docs.microsoft.com/javascript/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-js.
MIT License
2.07k stars 1.19k forks source link

Not able to read from event hub | Bug | @azure/event-hubs (5.12.1) #31350

Open sanjay-motorq opened 5 days ago

sanjay-motorq commented 5 days ago

Describe the bug Not able to read/receive messages from eventhub following official sdk documentation Code should be reading and logging eventhub messages but its not.

To Reproduce Steps to reproduce the behavior:

  1. Setup this code from sdk documentation
  2. Run the code

Expected behavior Read and log messages from eventhub

github-actions[bot] commented 5 days ago

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @kasun04.

deyaaeldeen commented 5 days ago

Hi @sanjay-motorq, I would be happy to assist you with your issue!

Could you please share more what issue are you facing? Also is the issue observable with an earlier version of the Event Hubs client library (e.g. v5.12.0)?

github-actions[bot] commented 5 days ago

Hi @sanjay-motorq. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

sanjay-motorq commented 5 days ago

Hi, it works with an earlier version of the library. The same code worked with 5.11.2 but did not work with the 5.12.1. Did not try with other versions.

deyaaeldeen commented 5 days ago

Thanks for your reply! I see, could you share more details what are the issues you're facing?

Also, I would recommend following the troubleshooting guide to perform basic troubleshooting steps. We typically find it helpful to inspect the logs.

github-actions[bot] commented 5 days ago

Hi @sanjay-motorq. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

alastairs commented 3 days ago

We have just lost a day to troubleshooting this issue, and can confirm it was introduced in the latest 5.12.1 point release. Here follows an Azure JS SDK log capture, with the headline being:

2024-10-11T10:40:12.903502167+01:00 azure:core-amqp:warning [connection-1] An error occurred while negotiating the cbs claim: MessagingError: The request with message_id "84987611-73a3-5440-9959-6560b45d0683" to "$cbs" endpoint timed out. Please try again later.
2024-10-11T10:40:12.903508388+01:00 azure:event-hubs:warning [connection-1] Sender REDACTED_HUB_NAME/Partitions/0: an error occurred while being created: MessagingError: The request with message_id "84987611-73a3-5440-9959-6560b45d0683" to "$cbs" endpoint timed out. Please try again later.
2024-10-11T10:38:52.863841816+01:00 azure:identity:info WorkloadIdentityCredential => Invoking getToken() of Client Assertion Credential
2024-10-11T10:38:52.864056429+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:38:52 GMT] : [] : @azure/msal-node@2.15.0 : Info - getTokenCache called
2024-10-11T10:38:52.864138883+01:00 azure:identity:info ClientAssertionCredential => More than one account was found authenticated for this Client ID and Tenant ID.
2024-10-11T10:38:52.864148601+01:00 However, no "authenticationRecord" has been provided for this credential,
2024-10-11T10:38:52.864155484+01:00 therefore we're unable to pick between these accounts.
2024-10-11T10:38:52.864159592+01:00 A new login attempt will be requested, to ensure the correct account is picked.
2024-10-11T10:38:52.864175602+01:00 To work with multiple accounts for the same Client ID and Tenant ID, please provide an "authenticationRecord" when initializing a credential to prevent this from happening.
2024-10-11T10:38:52.864224072+01:00 azure:identity:info ClientAssertionCredential => Silent authentication failed, falling back to interactive method.
2024-10-11T10:38:52.864284595+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:38:52 GMT] : [b903038a-6ebd-4267-88eb-5829f8285965] : @azure/msal-node@2.15.0 : Info - acquireTokenByClientCredential called
2024-10-11T10:38:52.865002210+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:38:52 GMT] : [b903038a-6ebd-4267-88eb-5829f8285965] : @azure/msal-node@2.15.0 : Info - Building oauth client configuration with the following authority: https://login.microsoftonline.com/78375574-4a4c-41a5-8b31-72e0374aa242/oauth2/v2.0/token.
2024-10-11T10:38:52.865540965+01:00 azure:identity:info ClientAssertionCredential => getToken() => SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:38:52.865562698+01:00 azure:identity:info ChainedTokenCredential => getToken() => Result for DefaultWorkloadIdentityCredential: SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:39:02.870969346+01:00 azure:identity:info WorkloadIdentityCredential => Invoking getToken() of Client Assertion Credential
2024-10-11T10:39:02.871282851+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:02 GMT] : [] : @azure/msal-node@2.15.0 : Info - getTokenCache called
2024-10-11T10:39:02.871488836+01:00 azure:identity:info ClientAssertionCredential => More than one account was found authenticated for this Client ID and Tenant ID.
2024-10-11T10:39:02.871630811+01:00 However, no "authenticationRecord" has been provided for this credential,
2024-10-11T10:39:02.871648624+01:00 therefore we're unable to pick between these accounts.
2024-10-11T10:39:02.871655607+01:00 A new login attempt will be requested, to ensure the correct account is picked.
2024-10-11T10:39:02.871662280+01:00 To work with multiple accounts for the same Client ID and Tenant ID, please provide an "authenticationRecord" when initializing a credential to prevent this from happening.
2024-10-11T10:39:02.871682938+01:00 azure:identity:info ClientAssertionCredential => Silent authentication failed, falling back to interactive method.
2024-10-11T10:39:02.871694750+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:02 GMT] : [20fbb047-e8af-4e6c-ae04-0f1d8d499178] : @azure/msal-node@2.15.0 : Info - acquireTokenByClientCredential called
2024-10-11T10:39:02.872116167+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:02 GMT] : [20fbb047-e8af-4e6c-ae04-0f1d8d499178] : @azure/msal-node@2.15.0 : Info - Building oauth client configuration with the following authority: https://login.microsoftonline.com/78375574-4a4c-41a5-8b31-72e0374aa242/oauth2/v2.0/token.
2024-10-11T10:39:02.872504362+01:00 azure:identity:info ClientAssertionCredential => getToken() => SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:39:02.872529950+01:00 azure:identity:info ChainedTokenCredential => getToken() => Result for DefaultWorkloadIdentityCredential: SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:39:12.877564850+01:00 azure:identity:info WorkloadIdentityCredential => Invoking getToken() of Client Assertion Credential
2024-10-11T10:39:12.877920903+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:12 GMT] : [] : @azure/msal-node@2.15.0 : Info - getTokenCache called
2024-10-11T10:39:12.877949867+01:00 azure:identity:info ClientAssertionCredential => More than one account was found authenticated for this Client ID and Tenant ID.
2024-10-11T10:39:12.877981966+01:00 However, no "authenticationRecord" has been provided for this credential,
2024-10-11T10:39:12.877989741+01:00 therefore we're unable to pick between these accounts.
2024-10-11T10:39:12.877996263+01:00 A new login attempt will be requested, to ensure the correct account is picked.
2024-10-11T10:39:12.878002504+01:00 To work with multiple accounts for the same Client ID and Tenant ID, please provide an "authenticationRecord" when initializing a credential to prevent this from happening.
2024-10-11T10:39:12.878008486+01:00 azure:identity:info ClientAssertionCredential => Silent authentication failed, falling back to interactive method.
2024-10-11T10:39:12.878014387+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:12 GMT] : [d660ea7d-4c78-4edb-8494-9cd7ba1f2d13] : @azure/msal-node@2.15.0 : Info - acquireTokenByClientCredential called
2024-10-11T10:39:12.878372974+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:12 GMT] : [d660ea7d-4c78-4edb-8494-9cd7ba1f2d13] : @azure/msal-node@2.15.0 : Info - Building oauth client configuration with the following authority: https://login.microsoftonline.com/78375574-4a4c-41a5-8b31-72e0374aa242/oauth2/v2.0/token.
2024-10-11T10:39:12.878666760+01:00 azure:identity:info ClientAssertionCredential => getToken() => SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:39:12.878824965+01:00 azure:identity:info ChainedTokenCredential => getToken() => Result for DefaultWorkloadIdentityCredential: SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:39:22.883239847+01:00 azure:identity:info WorkloadIdentityCredential => Invoking getToken() of Client Assertion Credential
2024-10-11T10:39:22.883456544+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:22 GMT] : [] : @azure/msal-node@2.15.0 : Info - getTokenCache called
2024-10-11T10:39:22.883549187+01:00 azure:identity:info ClientAssertionCredential => More than one account was found authenticated for this Client ID and Tenant ID.
2024-10-11T10:39:22.883576278+01:00 However, no "authenticationRecord" has been provided for this credential,
2024-10-11T10:39:22.883585625+01:00 therefore we're unable to pick between these accounts.
2024-10-11T10:39:22.883591977+01:00 A new login attempt will be requested, to ensure the correct account is picked.
2024-10-11T10:39:22.883598769+01:00 To work with multiple accounts for the same Client ID and Tenant ID, please provide an "authenticationRecord" when initializing a credential to prevent this from happening.
2024-10-11T10:39:22.883611333+01:00 azure:identity:info ClientAssertionCredential => Silent authentication failed, falling back to interactive method.
2024-10-11T10:39:22.883678799+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:22 GMT] : [9a1b4af6-66bd-455e-8c7f-b2a350b00e74] : @azure/msal-node@2.15.0 : Info - acquireTokenByClientCredential called
2024-10-11T10:39:22.884048456+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:22 GMT] : [9a1b4af6-66bd-455e-8c7f-b2a350b00e74] : @azure/msal-node@2.15.0 : Info - Building oauth client configuration with the following authority: https://login.microsoftonline.com/78375574-4a4c-41a5-8b31-72e0374aa242/oauth2/v2.0/token.
2024-10-11T10:39:22.884313671+01:00 azure:identity:info ClientAssertionCredential => getToken() => SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:39:22.884330592+01:00 azure:identity:info ChainedTokenCredential => getToken() => Result for DefaultWorkloadIdentityCredential: SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:39:32.890775870+01:00 azure:identity:info WorkloadIdentityCredential => Invoking getToken() of Client Assertion Credential
2024-10-11T10:39:32.890992687+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:32 GMT] : [] : @azure/msal-node@2.15.0 : Info - getTokenCache called
2024-10-11T10:39:32.891079810+01:00 azure:identity:info ClientAssertionCredential => More than one account was found authenticated for this Client ID and Tenant ID.
2024-10-11T10:39:32.891091061+01:00 However, no "authenticationRecord" has been provided for this credential,
2024-10-11T10:39:32.891098996+01:00 therefore we're unable to pick between these accounts.
2024-10-11T10:39:32.891105848+01:00 A new login attempt will be requested, to ensure the correct account is picked.
2024-10-11T10:39:32.891113302+01:00 To work with multiple accounts for the same Client ID and Tenant ID, please provide an "authenticationRecord" when initializing a credential to prevent this from happening.
2024-10-11T10:39:32.891161920+01:00 azure:identity:info ClientAssertionCredential => Silent authentication failed, falling back to interactive method.
2024-10-11T10:39:32.891224600+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:32 GMT] : [96672519-8cce-430e-baf4-33e467e5bb88] : @azure/msal-node@2.15.0 : Info - acquireTokenByClientCredential called
2024-10-11T10:39:32.891642126+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:32 GMT] : [96672519-8cce-430e-baf4-33e467e5bb88] : @azure/msal-node@2.15.0 : Info - Building oauth client configuration with the following authority: https://login.microsoftonline.com/78375574-4a4c-41a5-8b31-72e0374aa242/oauth2/v2.0/token.
2024-10-11T10:39:32.892016453+01:00 azure:identity:info ClientAssertionCredential => getToken() => SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:39:32.892039236+01:00 azure:identity:info ChainedTokenCredential => getToken() => Result for DefaultWorkloadIdentityCredential: SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:39:42.897257398+01:00 azure:identity:info WorkloadIdentityCredential => Invoking getToken() of Client Assertion Credential
2024-10-11T10:39:42.897367048+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:42 GMT] : [] : @azure/msal-node@2.15.0 : Info - getTokenCache called
2024-10-11T10:39:42.897464354+01:00 azure:identity:info ClientAssertionCredential => More than one account was found authenticated for this Client ID and Tenant ID.
2024-10-11T10:39:42.897476456+01:00 However, no "authenticationRecord" has been provided for this credential,
2024-10-11T10:39:42.897483219+01:00 therefore we're unable to pick between these accounts.
2024-10-11T10:39:42.897489401+01:00 A new login attempt will be requested, to ensure the correct account is picked.
2024-10-11T10:39:42.897499048+01:00 To work with multiple accounts for the same Client ID and Tenant ID, please provide an "authenticationRecord" when initializing a credential to prevent this from happening.
2024-10-11T10:39:42.897511732+01:00 azure:identity:info ClientAssertionCredential => Silent authentication failed, falling back to interactive method.
2024-10-11T10:39:42.897557337+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:42 GMT] : [0b021fb4-8658-4411-b85b-65d934436c51] : @azure/msal-node@2.15.0 : Info - acquireTokenByClientCredential called
2024-10-11T10:39:42.897872382+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:42 GMT] : [0b021fb4-8658-4411-b85b-65d934436c51] : @azure/msal-node@2.15.0 : Info - Building oauth client configuration with the following authority: https://login.microsoftonline.com/78375574-4a4c-41a5-8b31-72e0374aa242/oauth2/v2.0/token.
2024-10-11T10:39:42.898210522+01:00 azure:identity:info ClientAssertionCredential => getToken() => SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:39:42.898241289+01:00 azure:identity:info ChainedTokenCredential => getToken() => Result for DefaultWorkloadIdentityCredential: SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:39:42.899493564+01:00 azure:event-hubs:warning [connection-1] Sender REDACTED_HUB_NAME/Partitions/0: an error occurred while being created: MessagingError: Unable to create the amqp sender 'REDACTED_HUB_NAME/Partitions/0' on amqp session 'local-2_remote-2_connection-1' due to operation timeout.
2024-10-11T10:39:52.914744236+01:00 azure:identity:info WorkloadIdentityCredential => Invoking getToken() of Client Assertion Credential
2024-10-11T10:39:52.914893394+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:52 GMT] : [] : @azure/msal-node@2.15.0 : Info - getTokenCache called
2024-10-11T10:39:52.914985183+01:00 azure:identity:info ClientAssertionCredential => More than one account was found authenticated for this Client ID and Tenant ID.
2024-10-11T10:39:52.915004900+01:00 However, no "authenticationRecord" has been provided for this credential,
2024-10-11T10:39:52.915014999+01:00 therefore we're unable to pick between these accounts.
2024-10-11T10:39:52.915022763+01:00 A new login attempt will be requested, to ensure the correct account is picked.
2024-10-11T10:39:52.915030728+01:00 To work with multiple accounts for the same Client ID and Tenant ID, please provide an "authenticationRecord" when initializing a credential to prevent this from happening.
2024-10-11T10:39:52.915044914+01:00 azure:identity:info ClientAssertionCredential => Silent authentication failed, falling back to interactive method.
2024-10-11T10:39:52.915106670+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:52 GMT] : [766ac179-3488-48ab-b1ca-04e9313a5b21] : @azure/msal-node@2.15.0 : Info - acquireTokenByClientCredential called
2024-10-11T10:39:52.915691072+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:39:52 GMT] : [766ac179-3488-48ab-b1ca-04e9313a5b21] : @azure/msal-node@2.15.0 : Info - Building oauth client configuration with the following authority: https://login.microsoftonline.com/78375574-4a4c-41a5-8b31-72e0374aa242/oauth2/v2.0/token.
2024-10-11T10:39:52.916038280+01:00 azure:identity:info ClientAssertionCredential => getToken() => SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:39:52.916092381+01:00 azure:identity:info ChainedTokenCredential => getToken() => Result for DefaultWorkloadIdentityCredential: SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:40:02.919632944+01:00 azure:identity:info WorkloadIdentityCredential => Invoking getToken() of Client Assertion Credential
2024-10-11T10:40:02.919783264+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:40:02 GMT] : [] : @azure/msal-node@2.15.0 : Info - getTokenCache called
2024-10-11T10:40:02.919867591+01:00 azure:identity:info ClientAssertionCredential => More than one account was found authenticated for this Client ID and Tenant ID.
2024-10-11T10:40:02.919880134+01:00 However, no "authenticationRecord" has been provided for this credential,
2024-10-11T10:40:02.919889542+01:00 therefore we're unable to pick between these accounts.
2024-10-11T10:40:02.919897767+01:00 A new login attempt will be requested, to ensure the correct account is picked.
2024-10-11T10:40:02.919902987+01:00 To work with multiple accounts for the same Client ID and Tenant ID, please provide an "authenticationRecord" when initializing a credential to prevent this from happening.
2024-10-11T10:40:02.919960745+01:00 azure:identity:info ClientAssertionCredential => Silent authentication failed, falling back to interactive method.
2024-10-11T10:40:02.920052329+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:40:02 GMT] : [49f791df-6ee3-451f-80a0-da8d31ec2756] : @azure/msal-node@2.15.0 : Info - acquireTokenByClientCredential called
2024-10-11T10:40:02.920403819+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:40:02 GMT] : [49f791df-6ee3-451f-80a0-da8d31ec2756] : @azure/msal-node@2.15.0 : Info - Building oauth client configuration with the following authority: https://login.microsoftonline.com/78375574-4a4c-41a5-8b31-72e0374aa242/oauth2/v2.0/token.
2024-10-11T10:40:02.920763179+01:00 azure:identity:info ClientAssertionCredential => getToken() => SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:40:02.920906937+01:00 azure:identity:info ChainedTokenCredential => getToken() => Result for DefaultWorkloadIdentityCredential: SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:40:12.900627553+01:00 azure:identity:info WorkloadIdentityCredential => Invoking getToken() of Client Assertion Credential
2024-10-11T10:40:12.900731026+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:40:12 GMT] : [] : @azure/msal-node@2.15.0 : Info - getTokenCache called
2024-10-11T10:40:12.900810875+01:00 azure:identity:info ClientAssertionCredential => More than one account was found authenticated for this Client ID and Tenant ID.
2024-10-11T10:40:12.900820483+01:00 However, no "authenticationRecord" has been provided for this credential,
2024-10-11T10:40:12.900826725+01:00 therefore we're unable to pick between these accounts.
2024-10-11T10:40:12.900832616+01:00 A new login attempt will be requested, to ensure the correct account is picked.
2024-10-11T10:40:12.900838667+01:00 To work with multiple accounts for the same Client ID and Tenant ID, please provide an "authenticationRecord" when initializing a credential to prevent this from happening.
2024-10-11T10:40:12.903447675+01:00 azure:identity:info ClientAssertionCredential => Silent authentication failed, falling back to interactive method.
2024-10-11T10:40:12.903467712+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:40:12 GMT] : [994f6b39-12f9-45da-8571-361d40c08e37] : @azure/msal-node@2.15.0 : Info - acquireTokenByClientCredential called
2024-10-11T10:40:12.903474826+01:00 azure:identity:info ClientAssertionCredential => MSAL Node V2 info message: [Fri, 11 Oct 2024 09:40:12 GMT] : [994f6b39-12f9-45da-8571-361d40c08e37] : @azure/msal-node@2.15.0 : Info - Building oauth client configuration with the following authority: https://login.microsoftonline.com/78375574-4a4c-41a5-8b31-72e0374aa242/oauth2/v2.0/token.
2024-10-11T10:40:12.903480957+01:00 azure:identity:info ClientAssertionCredential => getToken() => SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:40:12.903487189+01:00 azure:identity:info ChainedTokenCredential => getToken() => Result for DefaultWorkloadIdentityCredential: SUCCESS. Scopes: https://eventhubs.azure.net//.default.
2024-10-11T10:40:12.903502167+01:00 azure:core-amqp:warning [connection-1] An error occurred while negotiating the cbs claim: MessagingError: The request with message_id "84987611-73a3-5440-9959-6560b45d0683" to "$cbs" endpoint timed out. Please try again later.
2024-10-11T10:40:12.903508388+01:00 azure:event-hubs:warning [connection-1] Sender REDACTED_HUB_NAME/Partitions/0: an error occurred while being created: MessagingError: The request with message_id "84987611-73a3-5440-9959-6560b45d0683" to "$cbs" endpoint timed out. Please try again later.
deyaaeldeen commented 3 days ago

Thanks @alastairs for sharing the logs. I am following up with the team on what are the possible issues that may cause authentication to time out but my initial thought is that the credential is not able to successfully authenticate for some reason.

In the meantime, could you please share more about how your application does authenticate into the Event Hubs resource and what credential it is using?

alastairs commented 3 days ago

Sure, we're using the DefaultAzureCredential object passed into the buffered producer's constructor. When deployed in AKS, this picks up the assigned workload identity credential.

We reverted to 5.12.0 across our environments earlier this afternoon, and the error has disappeared.

deyaaeldeen commented 2 days ago

@alastairs, @sanjay-motorq A fix has been released in v5.12.2.

github-actions[bot] commented 2 days ago

Hi @sanjay-motorq. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.