[ https://issues.apache.org/activemq/browse/AMQ-660?page=comments#action_35951 ]
Johan Hallgren commented on AMQ-660: ------------------------------------ OK, I got an answer back from one of the MaxDB devs. Apparently, the issue is a known bug, that is fixed in the latest 7.5 version of it (and assume in the 7.6 branch, too). Thus, long term there is no issue here. However, since I'm running it all on Debian Sarge, I'm relying on the Debian team to potentially backport the fix into their stable package version, or run their testing package of MaxDB instead. Until I can look into that, is the ACTIVEMQ_MSGS_EIDX index critical to the functioning of activemq, or can I drop it for now and still expect reasonable performance? > 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
