Emitter - Bridging the imperative and the reactive worlds

[giscus[bot]]

Emitter - Bridging the imperative and the reactive worlds

Quarkus: Supersonic Subatomic Java

https://quarkus.io/blog/reactive-messaging-emitter/

[fsomme2s]

How can I force the emitter to be synchronous / blocking? Running in a serverless context means I cannot wait for some background task to collect messages and send them "some point in the future" (because there is no future in serverless context)
...disclaimer: as far as I understand it now...

Actually when I try to use Emitter together with Quarkus for AWS Lambda, I get a "SRMSG00028: The subscription to mytopicname has been cancelled"

[josephearl]

+1

I thought using OnOverflow.Strategy.NONE (which then delegate to Mutiny BackPressureStrategy.IGNORE) would do this, but it doesn't (in my test case with this strategy messages get lost).

[bkalas]

Hi, if emitter emits to remote amqp broker,
you need to have in configuration mp.messaging.outgoing.<channelName>.* configuration.
Could you explain failure-strategy configurations for outgoing channels?
Do outgoing channels use this attribute? which of values fail (default), accept, release, reject, modified-failed are supported for outgoing?

[bkalas]

sorry should not be reply but new comment...

[bkalas]

Hi, if emitter emits to remote amqp broker,
you need to have in configuration mp.messaging.outgoing..* configuration.
Could you explain failure-strategy configurations for outgoing channels?
Do outgoing channels use this attribute? which of values fail (default), accept, release, reject, modified-failed are supported for outgoing?