[
https://issues.apache.org/jira/browse/AMQ-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705880#comment-13705880
]
Dejan Bosanac commented on AMQ-4628:
------------------------------------
One thing though is that this schema is not compatible with the previous
version if you're using XA transactions. You'll need to:
* Make sure you don't have an inflight transactions
* Stop the broker
* Alter the tables, by executing something like
{code}ALTER TABLE ACTIVEMQ_MSGS ALTER COLUMN XID VARCHAR(250)
CREATE INDEX ACTIVEMQ_MSGS_XIDX ON ACTIVEMQ_MSGS (XID)
ALTER TABLE ACTIVEMQ_ACKS ALTER COLUMN XID VARCHAR(250)
CREATE INDEX ACTIVEMQ_ACKS_XIDX ON ACTIVEMQ_ACKS (XID){code}
* Start the broker
This isn't needed if XA transactions are not used.
We need to put this into migration guide for 5.9
> Improve Performance of JDBC store with large number of messages
> ---------------------------------------------------------------
>
> Key: AMQ-4628
> URL: https://issues.apache.org/jira/browse/AMQ-4628
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.8.0
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.9.0
>
>
> Currently JDBC store doesn't behave well when there's a huge backlog of
> messages (like 1 million or more). With some SQL improvements, we can make it
> work properly for this use case as well.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
