[jira] [Commented] (ARTEMIS-3830) Lots of large messages prevent startup when using JDBC backend

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ARTEMIS-3830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17541051#comment-17541051 ] 

ASF subversion and git services commented on ARTEMIS-3830:
----------------------------------------------------------

Commit bf8e075ee7b1714c4c8b4f7a75e399307627c166 in activemq-artemis's branch refs/heads/main from Alexander Schwab
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=bf8e075ee7 ]

ARTEMIS-3830 add index on filename to large_messages


> 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
>
> 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)