[RIVER-245] Unicast discovery should close socket in case of connection exception.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: jtsk_2.1
• Fix Version/s: River_2.1.2
• Component/s: com_sun_jini_discovery
• Bugtraq ID: 6284047
• Assignee: Thomas Vinod Johnson
• Reporter: Jim Hurley
• Created: 14/Aug/07 19:46
• Updated: 06/Jan/10 06:04
• Resolved: 04/Mar/08 14:36

Description

Bugtraq 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).