You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Peter Jones (JIRA)" <ji...@apache.org> on 2008/05/01 17:16:55 UTC
[jira] Resolved: (RIVER-229) reduce number of Reaper threads
created by ConnectionManager
[ https://issues.apache.org/jira/browse/RIVER-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Jones resolved RIVER-229.
-------------------------------
Resolution: Fixed
> reduce number of Reaper threads created by ConnectionManager
> ------------------------------------------------------------
>
> Key: RIVER-229
> URL: https://issues.apache.org/jira/browse/RIVER-229
> Project: River
> Issue Type: Improvement
> Components: net_jini_jeri
> Affects Versions: jtsk_2.0
> Reporter: Jim Hurley
> Assignee: Peter Jones
> Priority: Minor
> Fix For: AR2
>
> Attachments: RIVER-229.patch
>
>
> Bugtraq ID [6291824|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6291824]
> Each ConnectionManager instance currently spawns its own Reaper thread to close down idle connections. If a client communicates with lots of different endpoints in a relatively short time interval, lots of threads get spawned. It should be possible to use a shared thread instead.
> See also Bugtraq ID 6319638
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.