[
https://issues.apache.org/jira/browse/AVRO-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966281#action_12966281
]
Doug Cutting commented on AVRO-704:
-----------------------------------
So you're saying that the SocketServer.Connection threads keep running after
the client has closed the connection? The expectation is that, when the remote
end closes the connection then the read attempt will fail and cause this thread
to exit.
Can you please provide a thread dump of this, with either 'kill -QUIT $pid' or
Control-backslash? Is the connecting client process still running at this
point? Is it possible that the client has not actually closed its connection?
Thanks!
> SockServer concurrency issues
> -----------------------------
>
> Key: AVRO-704
> URL: https://issues.apache.org/jira/browse/AVRO-704
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.4.1
> Reporter: Eric Evans
>
> The SocketServer does not shutdown threads when clients disconnect. Also,
> these "idle" threads seem to chew up a _lot_ of CPU. A simple echo server
> will peg the processor on my dev machine after accumulating just 2 or 3 of
> these threads.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
