[
https://issues.apache.org/jira/browse/AVRO-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966778#action_12966778
]
Eric Evans commented on AVRO-704:
---------------------------------
It gets set on the client and I think it only needs to be set on one end(?) At
any rate, I tried setting nodelay in the other constructor and it didn't effect
the results.
> 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
> Assignee: Doug Cutting
> Fix For: 1.5.0
>
> Attachments: AVRO-704.patch
>
>
> 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.
