[jira] Commented: (AMQ-660) Add support for MaxDB

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (AMQ-660) Add support for MaxDB

JIRA jira@apache.org
    [ https://issues.apache.org/activemq/browse/AMQ-660?page=comments#action_35971 ]

Johan Hallgren commented on AMQ-660:
------------------------------------

OK, I've manually dropped the offending index, and it seems not to be recreated by adding the <createSchemaStatements/> element to the config as explained above (were I to deploy activemq on a new machine using the same MaxDB version, I assume that I'd need first to start the broker without a createSchemaStatements tag to have it create the full schema, and then manually drop the insex, insert the element in activemq.xml and restart, correct?).

However, adding the deleteOldMessages attribute to the statements element gives this error when starting the broker:

ERROR: java.lang.RuntimeException: Failed to execute start task. Reason: org.springframework.beans.factory.BeanDefinitionStoreException: Line 26 in XML document from class path resource [activemq.xml] is invalid; nested exception is org.xml.sax.SAXParseException: The value of attribute "deleteOldMessagesStatement" associated with an element type "statements" must not contain the '<' character.
ERROR: java.lang.Exception: org.springframework.beans.factory.BeanDefinitionStoreException: Line 26 in XML document from class path resource [activemq.xml] is invalid; nested exception is org.xml.sax.SAXParseException: The value of attribute "deleteOldMessagesStatement" associated with an element type "statements" must not contain the '<' character.

Removing the less than character fixes the issue, but obviously makes the statement wrong. Is there some way to rewrite the less than character in activemq.xml?

Finally, so far I'm still using the statements attributes that were needed to get MaxDB to operate with MaxDB in the first place (binaryDataType ="LONG BYTE" longDataType ="INTEGER" stringIdDataType="VARCHAR(250) ASCII"). Can I remove them, now that the snapshots starting on 3/29 contain automatic support for MaxDB, or are they still needed?

> 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