Ozan Gunalp

Thank you for the reproducer! This is effectively the same as #21948. I am not sure why this happens but I think when the context propagation propagates the Tx context...

This is a head-scratcher for me too. What I think is happening is the schema auto-detection kicks in and it detects that it is not a avro/protobuf type and it...

And is `MyRecord` inside the app or compiled in another module and you add to your app with a dependency ?

Ok if you configure the bean discovery for the module defining avdl files (see `https://quarkus.io/guides/cdi-reference#how-to-generate-a-jandex-index`) you should have both main channel deserializer config and the DLQ serializer config auto generated...

It is generally wrong to put `@ActivateRequestContext` on an arbitrary method and expect things to work, especially when you need want to propagate information between request scoped beans. For the...

The PublisherDecorator#decorate method is called at startup time, on the main thread. When you have `@ActivateRequestContext` on that method you get the global request context state. Otherwise, the request context...

It'll be fixed in reactive messaging 4.17.0 The module causing the split package is only used in the quarkus reactive messaging extension. I think we can make the change in...

No, it'll be a part of reactive messaging 4.17

There is also the issue with `tracing-enabled=false` config not working for you. When not enabled that instrumenter isn't created at all.

@itatdcer I am creating the issue upstream but I'd like to keep this one for tracking purposes. I remember discussing this back then with @kabir, I think we still need...