[jira] Resolved: (RIVER-242) if a given ConnectionManager instance cannot create a reaper thread once, it never will again

["Peter Jones (JIRA)" <ji...@apache.org>]

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

Peter Jones resolved RIVER-242.
-------------------------------

    Resolution: Fixed

> if a given ConnectionManager instance cannot create a reaper thread once, it never will again
> ---------------------------------------------------------------------------------------------
>
>                 Key: RIVER-242
>                 URL: https://issues.apache.org/jira/browse/RIVER-242
>             Project: River
>          Issue Type: Bug
>          Components: net_jini_jeri
>    Affects Versions: jtsk_2.1
>         Environment: n/a
>            Reporter: Robert Resendes
>            Assignee: Peter Jones
>             Fix For: AR2
>
>
> Bugtraq ID [6319638|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6319638]
> When a ConnectionManager instance attempts to create a background thread for reaping idle (outbound) connections that it has created, if that attempt throws an OutOfMemoryError, then it will never try to create such a reaper thread again, because it will have already set its "reaper" field to a non-null value, which will falsely indicate to all future invocations of the same code that the reaper thread is already running (it only gets reset to null by a running reaper thread that is about to self-terminate).  This condition will cause all future connections made by that ConnectionManager instance to not time out naturally (ConnectionManager instances are per endpoint value).
> [Note that this bug will likely get fixed as part of the fix for RIVER-229 [Bugtraq ID 6291824], but it seemed important to file it as a distinct issue.]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.