Azure / Azure/azure-service-bus-java
Error occurred while refreshing token that is not retriable. Not scheduling refresh task.
- Lingua principale
- Java
- Stelle
- 62
- Fork
- 63
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
## Actual Behavior
1. Getting the error: " Error occurred while refreshing token that is not retriable. Not scheduling refresh task."
2.
## Expected Behavior
1. No error while refreshing the token
Apologies for the vague error description, but this is all I'm getting from my deployment logs. Below the full output:
2022-04-04 07:45:25,557 ERROR [com.azu.cor.amq.imp.ActiveClientTokenManager] (reactor-executor-2) Error occurred while refreshing token that is not retriable. Not scheduling refresh task. Use ActiveClientTokenManager.authorize() to schedule task again. audience[amqp://ddc-d-sbn.servicebus.windows.net/ddc-sbt-capture-results/subscriptions/capture-results-subscription] scopes[https://servicebus.azure.net/.default]
period >= 0 required but it was -1484075030000000000
## Versions
- OS platform and version: Linux, AKS
- Maven package version or commit ID: Latest
### Some more information:
I'm using AKS. I've followed the examples provided from these guides: https://docs.microsoft.com/nl-nl/azure/service-bus-messaging/service-bus-java-how-to-use-queues
Also, I'm using Managed ID as authentication. That should be implemented correctly, since I've also already implemented it for my Blob Storage code and that is working correctly.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start with ActiveClientTokenManager.authorize() and the deployment log showing the negative period value during managed-identity token refresh. Reproduce the failure in the stated AKS setup, then verify the token refresh completes without the non-retriable error and that refresh scheduling resumes.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- azure, java
- Ambito
- authentication, backend, cloud
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 25/100