[ https://issues.apache.org/activemq/browse/AMQ-660?page=comments#action_35972 ]
Johan Hallgren commented on AMQ-660: ------------------------------------ A further piece of input: I changed the deleteOldMessagesStatement to be "DELETE FROM ACTIVEMQ_MSGS WHERE ID = ( SELECT min(ACTIVEMQ_ACKS.LAST_ACKED_ID) FROM ACTIVEMQ_ACKS WHERE ACTIVEMQ_ACKS.CONTAINER=ACTIVEMQ_MSGS.CONTAINER) (I know that just dropping the < character probably makes the statement not very useful, but wanted to move past the error I reported above), and let the broker run for a while (with the ACTIVEMQ_MSGS_EIDX index dropped). I then get this message regularly: WARN JDBCPersistenceAdapter - Old message cleanup failed due to: com.sap.dbtech.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: Column index 1 was not found. Did my change of the delete statement cause the dropped index to be needed, or do I need to make other changes to the statements used? > 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
