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

Client may shtudown when failover connection is reconnecting. We need to maintain at least 1 non-daemon thread alive.

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 4.0, 5.3.0
    • 5.6.0, 4.0.3
    • None
    • None

    Description

      Dejan Reported on the User lists:

      Hi,

      after some experiments I found that this problem only exists if there are no
      other threads in the application. It seems like connection thread dies
      before it manages to reconnect. By starting another thread in the
      application, it succeeds to recover from master failure and reconnect to the
      slave broker. So I have a workaround for now, but it would be nice to make
      this work even for simple (single-threaded) clients.

      Regards,
      Dejan

      Attachments

        1. AMQ-796.cmd
          1 kB
          Gordon King
        2. jstack_amq_5.6.0
          20 kB
          Bhanu
        3. jstack_v5.8.0
          7 kB
          Bhanu
        4. Sender.java
          2 kB
          TuoDi
        5. threadDump.txt
          30 kB
          TuoDi

        Issue Links

          is fixed by

          Bug - A problem which impairs or prevents the functions of the product. AMQ-9483 Non Daemon Connection Keeping JVM alive when combined with optimizedAckScheduledAckInterval

          • Major - Major loss of function.
          • Open

          Activity

            People

              rajdavies Robert Davies
              chirino Hiram R. Chirino
              Votes:
              2 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: