Uploaded image for project: 'JGroups'
  1. JGroups
  2. JGRP-2306

Calling disconnect on StompConnection leads to logging an Error

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 4.0.16
    • 3.6.9
    • None
    • Hide

      1) call connect() on the StompConnection
      2) Wait until startRunner() has been called and the thread is at STOMP.readFrame(in)
      3) call disconnect()

      Show
      1) call connect() on the StompConnection 2) Wait until startRunner() has been called and the thread is at STOMP.readFrame(in) 3) call disconnect()

    Description

      When disconnect() is called in StompConnection it will change running to false and close the connections which can result in an uncaught IOException in the run loop which is logged as an Error.

      We desire to log errors, but if disconnect() has been called and running is no longer true then this should not be an unexpected error?

      Probably has been a thing for long time, looks like this loop has been in the code for many versions.

      Attachments

        Activity

          People

            rhn-engineering-bban Bela Ban
            linuxfreakus_jira Eric Nichols (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: