Azure / Azure/azure-functions-host

Investigation: disposal/stop paths ordering

Open
#5,651 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
C#
Stars
2k
Forks
482
Avg merge
2d 12h
Merged PRs (30d)
38

Description

A customer had an issue with an EventHub-triggered function which was throwing the error `DryIoc.ContainerException : Container is disposed and should not be used: Container is disposed.` on shutdown. We have determined from the logs that this is because the host is disposing before the RPC service. Disposal may be occurring in the stop path, and vice-versa.

related issue: #4190, and associated PR #4590.

Associated IcM incident: [175136273](https://icm.ad.msft.net/imp/v3/incidents/details/175136273/home)

@pragnagopa @yojagad @mhoeger @fabiocav

Contributor guide

Open the contributing guide

Research direction

Start by reading related issue #4190 and associated PR #4590, then trace the host and RPC disposal and stop paths implicated by the logs. Determine the shutdown ordering that causes the disposed-container error; done means the expected ordering is established and the host does not dispose before the RPC service.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.