activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johan Hallgren (JIRA)" <>
Subject [jira] Commented: (AMQ-660) Add support for MaxDB
Date Tue, 04 Apr 2006 14:28:59 GMT
    [ ] 

Johan Hallgren commented on AMQ-660:

A further piece of input: I changed the deleteOldMessagesStatement to be "DELETE FROM ACTIVEMQ_MSGS
(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:
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:
>      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:

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message