river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Vinod Johnson (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (RIVER-245) Unicast discovery should close socket in case of connection exception.
Date Tue, 04 Mar 2008 14:36:40 GMT

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

Thomas Vinod Johnson resolved RIVER-245.

    Resolution: Fixed

Submitted patch

> Unicast discovery should close socket in case of connection exception.
> ----------------------------------------------------------------------
>                 Key: RIVER-245
>                 URL: https://issues.apache.org/jira/browse/RIVER-245
>             Project: River
>          Issue Type: Bug
>          Components: com_sun_jini_discovery
>    Affects Versions: jtsk_2.1
>            Reporter: Jim Hurley
>            Assignee: Thomas Vinod Johnson
>            Priority: Minor
>             Fix For: AR2
>         Attachments: RIVER-245.patch
> Bugtraq ID [6284047|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6284047]
> The MultiIPDiscovery class which is used by ConstrainableLookupLocator, LookupDiscovery
and LookupLocatorDiscovery does not close the socket it created on encountering an exception
during connect. Ordinarily this should not result in the socket file descriptor being 'leaked'
(at least until finalization). However, this should still be cleaned up.
> This behavior would be consistent to the endpoint implementations too.
> We should also close those socket in case there is an exception while setting the SO_TIMEOUT
(setSoTimeout call).

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

View raw message