[jira] [Resolved] (KAFKA-2451) Exception logged but not managed

["Manikumar (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manikumar resolved KAFKA-2451.
------------------------------
    Resolution: Cannot Reproduce

 Pl reopen if you think the issue still exists


> Exception logged but not managed
> --------------------------------
>
>                 Key: KAFKA-2451
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2451
>             Project: Kafka
>          Issue Type: Bug
>          Components: producer 
>    Affects Versions: 0.8.1
>         Environment: Windows + Java
>            Reporter: Gwenhaël PASQUIERS
>            Assignee: Jun Rao
>
> We've been having issues with java-snappy and it's native dll.
> To make it short : we have exceptions when serializing the message.
> We are using kafka producer it in Camel.
> The problem is that kafka thinks that the message was worrectly sent, and returns no error: camel consumes the files even though kafka coult not send the messages.
> Where the issue lies (if i'm correct):
> In DefaultEventHandler line 115 with tag 0.8.1 the exception that is thrown by groupMessageToSet() is catched and logged. The return value of the function dispatchSerializedData() is used to determine if the send was successfull (if (outstandingProduceRequest.size >0) { ...}).
> BUT in this case I'm suspecting that, not even one message could be serialized and added to  "failedProduceRequests". So the code that called "dispatchSerializedData" thinks everything is OK though it's not.
> The producer could behave better and propagate the error properly. Since, it could lead to pure data loss.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)