Closed hgarus closed 1 month ago
It appears to be duplicate to this - https://github.com/spring-cloud/spring-cloud-function/issues/1174
This was resolved via a series of commits ins spring-cloud-stream
5d881b2ad 29a355832 058fc660a fac9eb1eb 14c10462f
As well as the commit in spring-cloud-function
It was alos back-ported to 4.1.x and will be available with the next release
Describe the issue Using the rabbitmq-Binder, with a consumer configured for consumer side batching as drescribed here, when a message is received, which is not convertible to the target type, the message is silently dropped.
To Reproduce
Useful to see what is actually happening (makes this less silent)
logging.level.org.springframework.cloud.function.context.config.JsonMessageConverter=debug
Send a message which cannot be converted to
MyDto
Version of the framework spring-boot 3.3.2 and spring cloud 2023.0.3 Expected behavior I would expect both messages to be DLQed instead. This would match the behaviour without batching, where an inconvertible Message is DLQed.
Additional context
The Example is a bit artificial, a more realistic example would be an unexpected Enum-Value.
This might also apply to the kafka-binder, I haven't tested that.