[
https://issues.apache.org/jira/browse/KAFKA-5595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090205#comment-16090205
]
Jason Gustafson edited comment on KAFKA-5595 at 7/17/17 6:23 PM:
-----------------------------------------------------------------
Ensuring connectionId uniqueness is a nice improvement, but I agree with Ismael
that it seems unlikely to fix the underlying issue. We may have to be content
with Rajini's logging improvements for now and hope that they will give us some
more hints the next time it happens. Seems extremely rare in any case.
One other data point worth mentioning: I mentioned the "Attempting to send
response via channel ..." messages above. In fact, there were about 13K of
these messages within 1 second of the illegal state exceptions.
was (Author: hachikuji):
Ensuring connectionId uniqueness is a nice improvement, but I agree with Ismael
that it seems unlikely to fix the underlying issue. We may have to be content
with the Rajini's logging improvements for now and hope that they will give us
some more hints the next time it happens. Seems extremely rare in any case.
One other data point worth mentioning: I mentioned the "Attempting to send
response via channel ..." messages above. In fact, there were about 13K of
these messages within 1 second of the illegal state exceptions.
> Illegal state in SocketServer; attempt to send with another send in progress
> ----------------------------------------------------------------------------
>
> Key: KAFKA-5595
> URL: https://issues.apache.org/jira/browse/KAFKA-5595
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
>
> I have seen this a couple times, but I'm not sure the conditions associated
> with it.
> {code}
> java.lang.IllegalStateException: Attempt to begin a send operation with prior
> send operation still in progress.
> at
> org.apache.kafka.common.network.KafkaChannel.setSend(KafkaChannel.java:138)
> at org.apache.kafka.common.network.Selector.send(Selector.java:248)
> at kafka.network.Processor.sendResponse(SocketServer.scala:488)
> at kafka.network.Processor.processNewResponses(SocketServer.scala:466)
> at kafka.network.Processor.run(SocketServer.scala:431)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> Prior to this event, I see a lot of this message in the logs (always for the
> same connection id):
> {code}
> Attempting to send response via channel for which there is no open
> connection, connection id 7
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
