Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-8153 Upgrade HornetQ for EAP 5.2.0
  3. JBPAPP-8067

CLONE - Paging won't expire messages unless there's an active consumer

    XMLWordPrintable

Details

    • Sub-task
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Done
    • EAP_EWP 5.1.2
    • EAP_EWP 5.2.0
    • HornetQ
    • None
    • Release Notes
    • An issue was identified with HornetQ where paged messages would not be expired if there was no active consumer. The expiry scan was enhanced so that it now includes paged messages in its analysis.
    • Documented as Resolved Issue
    • NEW

    Attachments

      Issue Links

        cloned from

        Bug - A problem which impairs or prevents the functions of the product. HORNETQ-843 Paging won't expire messages unless there's an active consumer

        • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
        • Closed

        Activity

          People

            csuconic@redhat.com Clebert Suconic
            csuconic@redhat.com Clebert Suconic
            Russell Dickenson Russell Dickenson (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: