You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/03/11 21:31:00 UTC

[jira] [Work logged] (ARTEMIS-4682) JDBC Storage slow to reboot the server

     [ https://issues.apache.org/jira/browse/ARTEMIS-4682?focusedWorklogId=909287&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-909287 ]

ASF GitHub Bot logged work on ARTEMIS-4682:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Mar/24 21:30
            Start Date: 11/Mar/24 21:30
    Worklog Time Spent: 10m 
      Work Description: clebertsuconic opened a new pull request, #4849:
URL: https://github.com/apache/activemq-artemis/pull/4849

   - fixing leaks
   - page.exists() would lead to a select(all) and find.




Issue Time Tracking
-------------------

            Worklog Id:     (was: 909287)
    Remaining Estimate: 0h
            Time Spent: 10m

> JDBC Storage slow to reboot the server
> --------------------------------------
>
>                 Key: ARTEMIS-4682
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-4682
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Clebert Suconic
>            Assignee: Clebert Suconic
>            Priority: Major
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> If you use JDBC storage and lots of message in paging mode, the JDBC storage will take a long time to load.
> There is a leak on the JDBC Sequential File Factory , and page.exists() is selecting every existing file to check its existance. not very efficient.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)