[
https://issues.apache.org/activemq/browse/AMQ-660?page=comments#action_35985 ]
Johan Hallgren commented on AMQ-660:
------------------------------------
Hiram,
Using the deleteOldMessagesStatement you specify above does make the "Column
index 1 was not found" go away, and the example producer and consumer still
work. I just have one remaining question:
The offending ACTIVEMQ_MSGS_IDX index still seems to be automatically created
on startup, even though I have the empty createSchemaStatements element in
activemq.xml like this:
<persistenceAdapter>
<journaledJDBC journalLogFiles="5" dataDirectory="../activemq-data"
dataSource="#maxdb-ds">
<statements>
<statements deleteOldMessagesStatement="DELETE FROM ACTIVEMQ_MSGS
WHERE <>? AND ID <= (SELECT min(ACTIVEMQ_ACKS.LAST_ACKED_ID) FROM
ACTIACTIVEMQ_ACKS WHERE ACTIVEMQ_ACKS.CONTAINER=ACTIVEMQ_MSGS.CONTAINER)"/>
<createSchemaStatements />
</statements>
</journaledJDBC>
</persistenceAdapter>
Do I need to nest the statements elements in some other way to get the
createSchemaStatements to have the desired effect?
> 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
