activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Tully <>
Subject Re: jdbc Master fails: AMQ v.5.6, Postgres v.9.1, Ubuntu
Date Mon, 11 Jun 2012 10:10:56 GMT
the correct impl should be picked up based on the type of the
underlying datasource. There is a mapper properties file that provides
overrides. ms sql server is the only driver that currently uses the
transact locker:

In the absence of doc, the best place to see what an individual config
option does it to check the source[1] One would only use the adapter
element if you want to explicitly provide the implementation, as in
the auto mapping is not correct.

Please open jira issues to trigger a doc enhancement so that the
experience is better for the next user.


On 11 June 2012 06:58, SergueiM <> wrote:
> metatech, thank you.
> The config piece that actually worked:
> <jdbcPersistenceAdapter ... >
>        <databaseLocker>
>                <database-locker queryTimeout="-1" />
>        </databaseLocker>
> </jdbcPersistenceAdapter>
> Folks,
> where one could read about those many options as in activemq-core.xsd?
> I could not find answers in AMQ docs, nor in Fuse docs, nor in the "ActiveMQ
> in Action" book.
> For example, in my context of jdbc Master/Slave:
> - when do I use database-locker as opposed to transact-database-locker?
> - disabling the setQueryTimeout (as in the above setting) affects/results in
> what?
> - what the "adapter" child element to jdbcPersistenceAdapter is for?
> Thank you.
> --
> View this message in context:
> Sent from the ActiveMQ - User mailing list archive at


View raw message