smallrye-reactive-messaging
smallrye-reactive-messaging copied to clipboard
smallrye
SmallRye Reactive Messaging
I'm using Smallrye-Kafka in my Quarkus application for connecting to kafka. Until now the requirement was "having a single bootstrap-server which is valid for all channels". The configuration and event...
I have observed that our heap slowly increasing with KafkaThrottledLatestProcessedCommit Here is the heap map Any inputs are greatly appreciated
Documentation [states](https://smallrye.io/smallrye-reactive-messaging/latest/amqp/receiving-amqp-messages/#deserialization): `The connector converts incoming AMQP Messages into Reactive Messaging Message instances. T depends on the body of the received AMQP Message.` In case of `AMQP Data (with binary...
For now SqsDeleteAckHandler and SqsOutboundChannel process the message separately (DeleteMessageRequest, SendMessageRequest) It's hard to work with FIFO queues they have limited capacity and it's required batch operations (DeleteMessageBatchRequest, SendMessageBatchRequest) It...
# Issue With the MQTT Connector, it is currently not possible to set the 'retain' property just by configuration for an outgoing MQTT channel. Now, instead of just returning or...
We use the existing failure management mechanism (described here https://smallrye.io/smallrye-reactive-messaging/4.20.0/rabbitmq/receiving-messages-from-rabbitmq/#failure-management) in order to allow retries of failed messages by putting it to a dead letter queue with a ttl. We...
Here, the password is logged on startup. This seemingly cannot be disabled and is bad practice. https://github.com/smallrye/smallrye-reactive-messaging/blob/11a6059635659e817e786f249e0b5f804b0674a0/smallrye-reactive-messaging-mqtt/src/main/java/io/smallrye/reactive/messaging/mqtt/Clients.java#L31-L33 Resolution proposition: Don't log the password.
When nacking SQS message I would expect it to the immediately returned back to the broker i.e. NACKing should set the VisibilityTimeout to 0. Current implementation does not seem to...
When we add a configuration in Quarkus to provide a custom ConsumerConfigurationData with the batchReceivePolicy provided ` @Produces @Identifier("goals") public ConsumerConfigurationData getConsumerGoalsConfig() { ConsumerConfigurationData data = new ConsumerConfigurationData(); data.setMaxPendingChunkedMessage(2000); data.setBatchReceivePolicy(...
