Uploaded image for project: 'ActiveMQ'
  1. ActiveMQ
  2. AMQ-6820

NIO transport should properly handle ClosedChannelException

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 5.15.0
    • Fix Version/s: 5.15.1, 5.16.0
    • Component/s: Transport
    • Labels:
      None

      Description

      The NIO transport does not properly handle a ClosedChannelException when it happens inside the SelectorSelection class. Instead of properly disposing of the transport it calls System.out.println() for the exception and keeps the transport alive. This caused a NPE later when the enable() method was called because the SelectionKey was null. The fix is to call onError() when the ClosedChannelException occurs so things get cleaned up and logged properly.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                cshannon Christopher L. Shannon
                Reporter:
                cshannon Christopher L. Shannon
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: