Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-10985

Duplicate Redeliveries on causing negative counters on paging after failover with dead consumers

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • EAP_EWP 5.3.0.ER1
    • EAP_EWP 5.2.0
    • HornetQ
    • None
    • Hide

      There will be two committs on the hornetq 2.2.eap5 branch. One for the test, one for the fix.. you can revert the fix and see the issue happening.

      Show
      There will be two committs on the hornetq 2.2.eap5 branch. One for the test, one for the fix.. you can revert the fix and see the issue happening.
    • Release Notes
    • Hide
      <para>During a failover, if there was a dead subscription when a producer was sending messages non-transactionally, and a consumer was consuming messages transactionally, this may have resulted in duplicate messages being delivered as well as causing negative counters on the destinations. This issue was fixed by syncing the page and the journal-page-counters, as well as correcting the cursor position on a destination with multiple subscribers.</para>
      Show
      <para>During a failover, if there was a dead subscription when a producer was sending messages non-transactionally, and a consumer was consuming messages transactionally, this may have resulted in duplicate messages being delivered as well as causing negative counters on the destinations. This issue was fixed by syncing the page and the journal-page-counters, as well as correcting the cursor position on a destination with multiple subscribers.</para>
    • Documented as Resolved Issue
    • NEW

      If you set a dead consumer on a destination,
      send messages non transactionally,
      and fail the

      Consume just one consumer transactionally...

      you could eventually have messages delivered in duplicate what will cause negative counters on these destinations, and of course having messages delivered in duplicate could be an issue.

      this is not an issue upstream (hornetQ 2.3 or 2.4 don't have this issue)

              csuconic@redhat.com Clebert Suconic
              csuconic@redhat.com Clebert Suconic
              Lucas Costi Lucas Costi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: