You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by directlx April 15, 2025
If an Error is thrown in the application's @KafkaListener listener code, such as an OOM, Spring Kafka catches this in MessagingMessageListenerAdapter and allows processing to continue, so the offsets are committed, and the message lost. (Unlike for an Exception where the offsets are not committed and message is retried). What is the rationale for this?
The text was updated successfully, but these errors were encountered:
Discussed in #3841
Originally posted by directlx April 15, 2025
If an Error is thrown in the application's @KafkaListener listener code, such as an OOM, Spring Kafka catches this in MessagingMessageListenerAdapter and allows processing to continue, so the offsets are committed, and the message lost. (Unlike for an Exception where the offsets are not committed and message is retried). What is the rationale for this?
The text was updated successfully, but these errors were encountered: