UIMA
  1. UIMA
  2. UIMA-2404

UIMA-AS session inactivity timer thread doesnt cleanup jms correctly

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.4.0AS
    • Component/s: Async Scaleout
    • Labels:
      None

      Description

      Session inactivity timer pops by default after 30 minutes of inactivity and it closes JMS connection to a broker. Current code first closes the connection and subsequently tries to close all JMS Sessions associated with the connection. It should be other way around, first close Sessions and than the Connection.

        Activity

        Hide
        Jerry Cwiklik added a comment -

        Reverse the order of JMS cleanup when the inactivity timer pops. Closes sessions and subsequently a connection to a broker.

        Show
        Jerry Cwiklik added a comment - Reverse the order of JMS cleanup when the inactivity timer pops. Closes sessions and subsequently a connection to a broker.

          People

          • Assignee:
            Unassigned
            Reporter:
            Jerry Cwiklik
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development