You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Benjamin Graf (Jira)" <ji...@apache.org> on 2020/03/10 12:25:00 UTC
[jira] [Comment Edited] (ARTEMIS-975) Reading messages from page
causes lost entries in db backend
[ https://issues.apache.org/jira/browse/ARTEMIS-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17055883#comment-17055883 ]
Benjamin Graf edited comment on ARTEMIS-975 at 3/10/20, 12:24 PM:
------------------------------------------------------------------
New info. I can see that those txs that are still available in the database are also still referenced in journal.transactions with non empty recordInfos list. All recordinfo items are from type 13 (ADD_RECORD_TX). Actually don't know where they are coming from.
was (Author: graben):
New info. I can see that those txs that are still available in the database are also still referenced in journal.transactions with non empty recordInfos list. Actually don't know where they are coming from.
> Reading messages from page causes lost entries in db backend
> ------------------------------------------------------------
>
> Key: ARTEMIS-975
> URL: https://issues.apache.org/jira/browse/ARTEMIS-975
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.0.0
> Reporter: Benjamin Graf
> Priority: Major
> Attachments: screenshot-1.png
>
>
> Consuming messages from pages with a db as persistence backend leaves commit records in message_table which doesn't get cleaned up. Seems that depaging does not add txids to internal map.
> SQL script for cleanup (no known side effect):
> {code}
> DELETE
> FROM MESSAGE_TABLE
> WHERE txid IN
> (SELECT txid
> FROM
> (SELECT count(*) AS cnt,
> txid
> FROM MESSAGE_TABLE
> WHERE txid IN
> (SELECT txid
> FROM MESSAGE_TABLE
> WHERE recordtype = 18)
> GROUP BY txid)AS m
> WHERE m.cnt=1)
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)