activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fred Toussi (JIRA)" <>
Subject [jira] [Commented] (AMQ-3922) HSQLDB support is broken as wrong data type is used in
Date Wed, 11 Jul 2012 14:46:38 GMT


Fred Toussi commented on AMQ-3922:

Sorry, cannot test as don't use ActiveMQ. Reporting due to HSQLDB concerns. It should work
if the CREATE TABLE defines the type as BLOB.

Also noted the BytesJDBCAdaptor simply contains redundant redefinitions of setBinaryData and
getBinaryData methods in the superclass.
> HSQLDB support is broken as wrong data type is used in
> -----------------------------------------------------------------------------
>                 Key: AMQ-3922
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.6.0
>            Reporter: Fred Toussi
> The HsqldbJDBCAdaptor defines the SQL type used for storing a lob as "OTHER". This is
wrong in principle, as this type is intended for storing complex serialized objects, not specifically
lobs. With this type, the JDBC setObject and getObject methods must be used to store and retrieve
the object (which is not the case with ActiveMQ).
> The problem has been encountered and reported in TOMEE-233 and elsewhere.
> With HSQLDB version 2.x, the type "BLOB" should be used for maximum storage capacity
and minimum memory use by the database engine. This type is supported in all modes of operation,
including in-memory and file databases.
> It seems a simple switch from "OBJECT" to "BLOB" in the code should do the job, as the
JDBC setBytes and getBytes methods used by the superclass are compatible with the BLOB type.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message