[
https://issues.apache.org/jira/browse/ARTEMIS-3830?focusedWorklogId=773597&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-773597
]
ASF GitHub Bot logged work on ARTEMIS-3830:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/May/22 16:59
Start Date: 23/May/22 16:59
Worklog Time Spent: 10m
Work Description: asfgit closed pull request #4077: ARTEMIS-3830 add
index on filename to large_messages
URL: https://github.com/apache/activemq-artemis/pull/4077
Issue Time Tracking
-------------------
Worklog Id: (was: 773597)
Remaining Estimate: 0h
Time Spent: 10m
> Lots of large messages prevent startup when using JDBC backend
> --------------------------------------------------------------
>
> Key: ARTEMIS-3830
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3830
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.19.0
> Reporter: Corona Borealis
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When using the JDBC backend and a lot of messages are stored in the table
> LARGE_MESSAGES (in my case > 1GB and > 1000 messages) and the broker is
> restarted, it is no longer able to complete the startup.
> On startup, the broker tries to load all the messages one by one, but because
> there is no corresponding index on the table, this results in a timeout
> exception.
> The query used is:
> {{select-file-by-filename=SELECT ID, FILENAME, EXTENSION, DATA FROM %s WHERE
> fileName=?}}
> but fileName does not have an index.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
