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
I'm using vertx-kafka-client 3.9.1.
When i meant to send a message ("abc") to consumer, i got an exception in handler function. After that, i tried to send another message ("xyz"), but my handler function didnt receive the message.
Is it a bug ? It should have received a new message despite exception in handler function.
I got the same issue with the Rxified version.
I was using a Json Deserializer for consumer, when I produce a non-Json value, I got a SerializationException. Even though, I caught the exception, the next values are nowhere to find.
consumer
.subscribe(kafkaTopic)
.toObservable()
.flatMap(someOerartor)
.doOnError(
error -> {
// do some error Handling
})
.doOnError(error -> {})
.subscribe(logger::info, logger::warn);
You have a "poison pill" in your topic, and in that case (be it with the standard Kafka client or the Vert.x Kafka client) you have head-of-the-line-blocking.
One strategy is, in the error handling function to check the class of the Exception, and if it's a RecordDeserializationException , get the topic, the partition and the offset, and manually commit it. This way, future polling made by the consumer will retrieve more records.
#220 has code samples (not Rx, but this is translatable) to do so.
I'm using vertx-kafka-client 3.9.1.
When i meant to send a message ("abc") to consumer, i got an exception in handler function. After that, i tried to send another message ("xyz"), but my handler function didnt receive the message.
Is it a bug ? It should have received a new message despite exception in handler function.
The text was updated successfully, but these errors were encountered: