[
https://issues.apache.org/activemq/browse/AMQ-660?page=comments#action_35952 ]
Hiram Chirino commented on AMQ-660:
-----------------------------------
Outstanding.
Thank you for looking into this. The ACTIVEMQ_MSGS_EIDX only helps durring
periodic batch job that does message cleanup. So it does not impact too much.
If you don't use message expirtation, you can avoid needing the index at all.
Just set the statements confiuration so it's something like:
<statements deleteOldMessagesStatement="DELETE FROM ACTIVEMQ_MSGS WHERE ID <= (
SELECT min(ACTIVEMQ_ACKS.LAST_ACKED_ID) FROM ACTIVEMQ_ACKS WHERE
ACTIVEMQ_ACKS.CONTAINER=ACTIVEMQ_MSGS.CONTAINER)"/>
If you want to stop activeMQ for trying to auto create the tables for you,
configure the statements element as follows.
<persistenceAdapter>
<journaledJDBC>
<statements>
<statements>
<createSchemaStatements/>
</statements>
</statements>
</journaledJDBC>
</persistenceAdapter>
> Add support for MaxDB
> ---------------------
>
> Key: AMQ-660
> URL: https://issues.apache.org/activemq/browse/AMQ-660
> Project: ActiveMQ
> Type: New Feature
> Components: Message Store
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 4.0 RC 2
> Attachments: activemq.log, activemq.log
>
>
> Originaly reported on the user mailing list:
> http://www.nabble.com/Adding-support-for-MaxDB-in-ActiveMQ-JDBC-persistence-layer-t1334466.html#a3572564
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
