Ozan Gunalp

I'll check that, it needs a patch release to reactive messaging.

This is normal, you should not assume that the send operation, even with the in-memory connector, is synchronous. So in the next line, you should have something like the following...

No, it wouldn't work either on 3.7.2. Again you are trying to replace an internal channel `data-stream` with an in-memory test connector.

For the async aspect of in-memory tests, I agree that it wasn't the case before. @jponge do you think this can be related to the queue implementation change in Mutiny...

> I am sure kafka example project is working well before, check [my link of the build result](https://github.com/hantsy/quarkus-sandbox/commit/295c6852e02d116aa47bff5d19ac9fb41c6dd101) for it. And it never threw such an exception like the connector...

> I'd be surprised if the queue provider change has had any impact, but if you find something let's dig it 👍 I'll also need to debug that...

> @ozangunalp Got new exceptions in the _kafka_ and _pulsar_ examples after renamed the `data-stream` to `messages-stream`. > > ```shell > Caused by: jakarta.enterprise.inject.spi.DeploymentException: > java.lang.IllegalArgumentException: > SRMSG00071: Invalid channel...

Fixed the import sort

@vsevel thank you for testing it out. It was supposed to work this way from the beginning.

Yes, I think I need to revert the pattern variable change for the backporting.