[ https://issues.apache.org/activemq/browse/AMQ-660?page=comments#action_35982 ]
Hiram Chirino commented on AMQ-660: ----------------------------------- Hi Johan, With a new server, you could always run the DDL manually against the DB. As for the < issue and the "Column index 1 was not found" ... try using: <statements deleteOldMessagesStatement="DELETE FROM ACTIVEMQ_MSGS WHERE 0<>? AND ID <= ( SELECT min(ACTIVEMQ_ACKS.LAST_ACKED_ID) FROM ACTIVEMQ_ACKS WHERE ACTIVEMQ_ACKS.CONTAINER=ACTIVEMQ_MSGS.CONTAINER)"/> > 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