Mailing-List: contact river-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: river-dev@incubator.apache.org
Message-ID: <11128586.1187120850547.JavaMail.jira@brutus>
Date: Tue, 14 Aug 2007 12:47:30 -0700 (PDT)
From: "Jim Hurley (JIRA)" <jira@apache.org>
To: river-commits@incubator.apache.org
Subject: [jira] Created: (RIVER-245) Unicast discovery should close socket
 in case of connection exception.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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
            Priority: Minor


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.