activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johan Hallgren" <>
Subject RE: Adding support for MaxDB in ActiveMQ JDBC persistence layer
Date Fri, 24 Mar 2006 14:54:50 GMT
Hi James,

Thanks for your swift reply. I tried to follow the tips in
to enable the persistance tables to be created on MaxDB, and found that with these data type
definition changes, the tables could be created:

    <journaledJDBC journalLogFiles="5" dataDirectory="../activemq-data" dataSource="#maxdb-ds">
        <statements binaryDataType ="LONG BYTE" longDataType ="INTEGER" stringIdDataType="VARCHAR(250)

MaxDB uses INTEGER for all types of integer numbers and LONG BYTE for a large binary object.
Also, MaxDB only allows a total primary key field length of 1024 bytes per table, so if you
try and create the persistance layer in a Unicode database instance you have to explicitly
set the stringIdDataType to ASCII as above (and it doesn't hurt to do it even if you run an
ASCII database instance).

Anyway, now when I try to start the broker, I get all normal-looking INFO messages in the
console window, execpt for these two:

WARN  JDBCPersistenceAdapter         - Database driver NOT recognized: [sap_db].  Will use
default JDBC implementation.
WARN  JDBCPersistenceAdapter         - Old message cleanup failed due to:
[-9404]: System error: AK System error: VAK724 1

The startup then proceeds to state that the message broker has started, but the second of
the above WARN messages then repeat whenever cleanup is attempted.

I am hoping that thses changes cover what needs to be done as regards tweaking the datatypes.
How can I find out what the JDBC connection type name is for the MaxDB JDBC driver, so that
it can be added to ActiveMQ? Also, is there a way to have the example producer and consumer
in use persistent storage to test that it actually works
with MaxDB (the producer output says "Using non-durable publishing", so I assume the persistence
layer is never used there)?

Any further insight much appreciated!

/Johan H

-----Original Message-----
From: James Strachan []
Sent: Fri 3/24/2006 7:57 AM
Subject: Re: Adding support for MaxDB in ActiveMQ JDBC persistence layer
Hi Johan

So mostly we need to work out the flavour of SQL that MaxDB supports
and to figure out what the DDL should look like etc. We have a number
of JDBC adaptors for the various different drives together with how
they handle data types and blobs etc. It could be we just need to
write one for MaxDB.

Also it could be we need to tweak a little the SQL data types we use -
I"ve just added a new section to this page describing how to do

Once we basically know the right combination of options that work for
MaxDB, we can add an entry into ActiveMQ so that we auto-discover the
database from the JDBC connection type name and do the right thing.

e.g. here is the current list of auto-discovered configurations of
JDBC, where the file name is the JDBC connection type name returned
from the JDBC driver


On 3/23/06, Johan Hallgren <> wrote:
> Hi list,
> I am currently in the process of evaluating ActiveMQ. Reading
I see that it supports quite a lot of databases, but unfortunately not the one that my company
is using (MaxDB (formerly SAPDB), I try to configure
activemq to use it by copying its JDBC jar file to activemq's lib directory, and configuring
activemq.xml to use it like this:
>   <bean id="maxdb-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close">
>     <property name="driverClassName" value=""/>
>     <property name="url" value="jdbc:sapdb://localhost/DatabaseInstanceName"/>
>     <property name="username" value="activemquser"/>
>     <property name="password" value="activemquser"/>
>   </bean>
> I used the MySQL sample config section as a template and substituted values for my MaxDB
instance (the class value I used as is, since I didn't know what to use there). However, when
starting ActiveMQ, I get these errors (I have created the database user mentioned above, but
not created any tables in that schema):



  • Unnamed multipart/mixed (inline, None, 0 bytes)
View raw message