[jira] Created: (AMQ-2470) JMS clients stalled in case of many messages on a different queue - JDBC persistence

JMS clients stalled in case of many messages on a different queue - JDBC persistence
------------------------------------------------------------------------------------

                 Key: AMQ-2470
                 URL: https://issues.apache.org/activemq/browse/AMQ-2470
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.3.0
         Environment: direct JDBC persistence to external database, large amount of message on a queue.
            Reporter: Gary Tully
            Assignee: Gary Tully
             Fix For: 5.4.0


With a large amount of messages in a Queue > 2M, the cleanup task takes a long time, maybe 20 minutes. Then it starts again immediately, which continually hogs the database as it locks out other users or other destinations.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/activemq/browse/AMQ-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-2470:
----------------------------

    Component/s: Message Store
    Environment: direct JDBC persistence to external MySQL database, large amount of message on a queue.   (was: direct JDBC persistence to external database, large amount of message on a queue. )

> JMS clients stalled in case of many messages on a different queue - JDBC persistence
> ------------------------------------------------------------------------------------
>
>                 Key: AMQ-2470
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2470
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.3.0
>         Environment: direct JDBC persistence to external MySQL database, large amount of message on a queue.
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.4.0
>
>
> With a large amount of messages in a Queue > 2M, the cleanup task takes a long time, maybe 20 minutes. Then it starts again immediately, which continually hogs the database as it locks out other users or other destinations.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/activemq/browse/AMQ-2470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-2470.
-----------------------------

    Resolution: Fixed

cleanup task now has fixed delay period rather than fixed rate. The cleanupPeriod is now the delay between the end of task completion and the next run. This ensures it will not hog the db.

> JMS clients stalled in case of many messages on a different queue - JDBC persistence
> ------------------------------------------------------------------------------------
>
>                 Key: AMQ-2470
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2470
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Message Store
>    Affects Versions: 5.3.0
>         Environment: direct JDBC persistence to external MySQL database, large amount of message on a queue.
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>             Fix For: 5.4.0
>
>
> With a large amount of messages in a Queue > 2M, the cleanup task takes a long time, maybe 20 minutes. Then it starts again immediately, which continually hogs the database as it locks out other users or other destinations.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.