In-memory connector regression with external library messaging in Quarkus 3.21.4 - Fixed in 3.24.1?

[micaelsf]

Hi everyone,

I'm experiencing what appears to be a regression introduced in Quarkus 3.21.4 related to the in-memory connector and external library integration.

The Problem:

• External library (injected via @InjectSpy) contains internal messaging emitters (kafka)

• When called from @incoming message processing methods, the external library's async operations hang indefinitely

• The same external library calls work perfectly when triggered from HTTP endpoints

• Both contexts use the in-memory connector configuration

Setup:

• External library uses internal @channel emitters for async operations

• Channels properly configured for in-memory via test resource manager

• Issue only manifests in messaging context, not HTTP context

• Worked correctly before Quarkus 3.21.4 upgrade

Current Workaround:

Mocking the external library's async methods instead of relying on the in-memory connector integration.

Question:

Has this regression with in-memory connector + external library messaging integration been identified and resolved in Quarkus 3.24.1?

Thanks for any insights!

[cescoffier]

Could you provide a reproducer?

@ozangunalp FYI. PRetty sure it's because of the duplicated context change

[ozangunalp]

We'd need a reproducer to pinpoint the issue. @cescoffier yes most probably the duplicated context issue is the reason.