You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Manikumar (JIRA)" <ji...@apache.org> on 2018/05/28 18:11:00 UTC

[jira] [Resolved] (KAFKA-5346) Kafka Producer Failure After Idle Time

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

Manikumar resolved KAFKA-5346.
------------------------------
    Resolution: Not A Problem

Closing as per above comment. Please reopen if you think the issue still exists

> Kafka Producer Failure After Idle Time
> --------------------------------------
>
>                 Key: KAFKA-5346
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5346
>             Project: Kafka
>          Issue Type: Bug
>         Environment: 0.9.0.1 , windows
>            Reporter: Manikandan P
>            Priority: Major
>              Labels: windows
>
> We are using kafka (2.11-0.9.0.1) in windows and using .NET Kafka SDK (kafka-net) for connecting kafka server.
> When we produce the data to kafka server after 15 minutes of idle time of .NET Client, we are getting below exception in the Kafka SDK Logs.
> TcpClient Socket [http://10.X.X.100:9092//10.X.X.211:50290] Socket.Poll(S): Data was not available, may be connection was closed. 
> TcpClient Socket [http://10.X.X.100:9092//10.X.X.211:50290] has been closed successfully.
> It seems that Kafka Server is accepting the socket request but not responding the request due to which we are not able to produce the message to Kafka even though Kafka Server is online.
> We also tried to increase the threads and also decrease the idle time in server.properties as below in kafka Server and still getting above logs.
> num.network.threads=6
> num.io.threads=16
> connections.max.idle.ms =120000
> Please help us to resolve the above issue as it is breaking functional flow and we are having in go live next week.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)