River
  1. River
  2. RIVER-245

Unicast discovery should close socket in case of connection exception.

    Details

    • Bugtraq ID:
      6284047

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

      1. RIVER-245.patch
        3 kB
        Thomas Vinod Johnson

        Activity

        Hide
        Thomas Vinod Johnson added a comment -

        Shouldn't have 'resolved', just set the Fix version to AR2.

        Show
        Thomas Vinod Johnson added a comment - Shouldn't have 'resolved', just set the Fix version to AR2.
        Hide
        Thomas Vinod Johnson added a comment -

        Patch file for this issue.

        Show
        Thomas Vinod Johnson added a comment - Patch file for this issue.
        Hide
        Thomas Vinod Johnson added a comment -

        Submitted patch

        Show
        Thomas Vinod Johnson added a comment - Submitted patch

          People

          • Assignee:
            Thomas Vinod Johnson
            Reporter:
            Jim Hurley
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development