[
https://issues.apache.org/jira/browse/AMQ-6049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010878#comment-15010878
]
Dejan Bosanac commented on AMQ-6049:
------------------------------------
The solution is supposed to limit the number of rows based on maxRows property
of the persistence adapter, like
{code}<persistenceAdapter>
<jdbcPersistenceAdapter dataDirectory="${activemq.data}"
dataSource="#oracle-ds" maxRows="1000"/>
</persistenceAdapter>{code}
I don't see any reason for this value to be greater than the largest page size
any destination is using.
> Add option to limit results from expensive queries
> --------------------------------------------------
>
> Key: AMQ-6049
> URL: https://issues.apache.org/jira/browse/AMQ-6049
> Project: ActiveMQ
> Issue Type: Improvement
> Components: JDBC
> Affects Versions: 5.12.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.13.0
>
>
> When using priority messages with JDBC store, a query that recovers messages
> from the db can be very expensive due to the sorting it has to do. The best
> way I found to improve the performance of that query is to limit the sorting
> set by limiting the number of entries expected from the query. This assumes
> changing the actual query and is vendor specific.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
