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

Stomp client is not removed from the broker on client disconnect

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 4.0
    • 5.2.0
    • Transport
    • None
    • Linux, Java 1.5.0_06

    Description

      If Stomp client crashes (or disconnects unexpectedly) when there are unconsumed messages in the broker, the subscriptions are not removed from the broker and some phantom consumer is still consuming messages. If you connect other client, it receives only half messages (other half messages goes to that phantom consumer still left afrter client disconnect). There are no error logs in activemq logs. We are using stomp client, whith client acknowledge mode, so on broker restart, all messages are delivered properly. You can also see in jmx console, that subscription still exists whithout any connection left.

      Attachments

        1. dumpemu4.png
          40 kB
          Tom Vijlbrief
        2. patch.txt
          0.6 kB
          Tom Vijlbrief
        3. patchInactivityMonitor.txt
          0.8 kB
          Tom Vijlbrief
        4. SessionState.patch
          0.3 kB
          Danielius Jurna
        5. StompScriptComplete.txt
          0.1 kB
          Martin Ronner
        6. StompScriptNoDisconnect.txt
          0.1 kB
          Martin Ronner
        7. StompSubscriptionRemoveTest.java
          7 kB
          Danielius Jurna

        Issue Links

          Activity

            People

              rajdavies Robert Davies
              jurna Danielius Jurna
              Votes:
              3 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: