Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-7518

commit records are leaking on JDBC journal after the whole data is consumed

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Undefined Undefined
    • None
    • AMQ 7.8.4.GA
    • jdbc
    • None
    • False
    • None
    • False
    • Hide

      Do not use HDR_DUPLICATE_DETECTION_ID property

      Show
      Do not use HDR_DUPLICATE_DETECTION_ID property
    • Hide
      • Add JDBC store to EAP configuration
      • Start JBoss EAP server
      • Send 1000 messages to testQueue
      • consume 1000 message from testQueue
      • log into the database (attached config uses Postgres) run query
      • select count from message_tbl ;
      • The above query should return 0 rows but it does not.
      Show
      Add JDBC store to EAP configuration Start JBoss EAP server Send 1000 messages to testQueue consume 1000 message from testQueue log into the database (attached config uses Postgres) run query select count from message_tbl ; The above query should return 0 rows but it does not.

      AMQ broker with JDBC persistence store leaks records in messaging table. When I send 1000 messages to the broker I can see 400 rows in the table:

      jbossdb=# select count from message_tbl ;
      count
      -------
      4000
      (1 row)
      jbossdb=#
      

      After consuming all message I would expect to see the table empty but this is not the case. I see 2000 rows:

       

      jbossdb=# select count from message_tbl ;
      count
      -------
      2000
      (1 row)
      jbossdb=# 
      

       
      If I repeat the above I see another 200 rows after all messages have been consumed. It looks to me like for each consumed message two rows are added to the table. As far as I can tell those rows are never deleted.

            rhn-support-jbertram Justin Bertram
            rhn-support-toross Tom Ross
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: