Scoped Filters give ObjectDisposed Exception

[gungorenu]

Hello,

Not sure if it is my fault for setting up something wrong so asking here. it would be nice if I can get some insight on the failure since it seems not related to my ServiceProvider.

I am trying to add OpenTelemetry tracing propagation and we use Scoped Filters as defined here: https://masstransit-project.com/advanced/middleware/scoped.html. gist is just an example. MT supports traces already but we want to add more stuff to that activity to enable support for stuff which does not have anything like headers/trace ids etc. it can be done in better ways perhaps but it does not change the test result I believe.

Code for test is available here: https://gist.github.com/gungorenu/6a6997ca7d463caef09b7fdddbf5efc7

the service provider I create is not disposed, or I do not dispose it but the provider accessed by DependencyInjectionScopeServiceProvider gets sth disposed already and not sure why. at lines 279-281 we can enable/disable filters and see which tests fail or pass. in my experience:

• enabling only consume or send or publish filter: all pass
• enabling send and publish filter: all pass
• enabling consume and send filter: all fail, ObjectDisposedException
• enabling consume and publish filter: the TimeMachine prefix tests (which use Future) fail, others pass
• enabling all : all fail, same as consume and send filters

I suspect the consume filter triggers something which causes the problem.

MT 8 develop branch is used for these, so latest code of MT. just run the tests in MT code and observe results. we have a similar setup and the trace filters are same

any idea what I am doing wrong here? there are similar tests already using scoped filters and they are green already but they do not have similar setup so I suspect I do something wrong with my test environment, but not sure what.

Thanks

[phatboyg]

If you are using scoped filters with the InMemoryOutbox, you need to configure the use of message scope prior to the outbox.

This is covered: #3310 (comment)

[ugugun]

the mentioned conversation fixed the problem. thanks a lot