kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prashanth Menon (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (KAFKA-305) SyncProducer does not correctly timeout
Date Thu, 15 Mar 2012 13:11:39 GMT
SyncProducer does not correctly timeout

                 Key: KAFKA-305
                 URL: https://issues.apache.org/jira/browse/KAFKA-305
             Project: Kafka
          Issue Type: Bug
          Components: core
    Affects Versions: 0.7, 0.8
            Reporter: Prashanth Menon
            Priority: Critical

So it turns out that using the channel in SyncProducer like we are to perform blocking reads
will not trigger socket timeouts (though we set it) and will block forever which is bad. 
This bug identifies the issue: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4614802
and this article presents a potential work-around: http://stackoverflow.com/questions/2866557/timeout-for-socketchannel
for workaround. The work-around is a simple solution that involves creating a separate ReadableByteChannel
instance for timeout-enabled reads.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message