Latest OrchestrationSessionManager changes are throwing unhandled exceptions in Azure.
- Lingua principale
- C#
- Stelle
- 1.7k
- Fork
- 335
- Merge medio
- 2g 23h
- PR unite (30g)
- 6
Descrizione
The line for the exception looks ok, so not sure what the reason is. I do not have a local environment to debug this project. I have been running for over a year and after upgrading to recent release, this happens very frequently and doesn't recover.
Application: w3wp.exe CoreCLR Version: 4.6.28008.2 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException: Object reference not set to an instance of an object. at DurableTask.AzureStorage.OrchestrationSessionManager.AddMessageToPendingOrchestration(ControlQueue controlQueue, IEnumerable`1 queueMessages, Guid traceActivityId, CancellationToken cancellationToken) in C:\source\durabletask\src\DurableTask.AzureStorage\OrchestrationSessionManager.cs:line 169 at DurableTask.AzureStorage.OrchestrationSessionManager.DequeueLoop(String partitionId, ControlQueue controlQueue, CancellationToken cancellationToken) in C:\source\durabletask\src\DurableTask.AzureStorage\OrchestrationSessionManager.cs:line 117 at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location where exception was thrown --- at System.Threading.ThreadPoolWorkQueue.Dispatch()
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Inizia leggendo DurableTask.AzureStorage/OrchestrationSessionManager.cs alle righe 169 e 117, utilizzando gli stack frame segnalati AddMessageToPendingOrchestration e DequeueLoop come punti di ingresso. Traccia la NullReferenceException dall’errore Azure segnalato e stabilisci quale modifica è necessaria affinché il processo non termini più con questa eccezione non gestita.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- azure, csharp
- Ambito
- 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