On 8/22/06, Terry Cox <[EMAIL PROTECTED]> wrote:
> Howl is a transaction log, i.e. it will store into a file informations
> related to
> xa transactions while preparing / committing the transactions.
> It' s not a persistence layer.
I worked it out. The activeMQ docs are missing the config parameter to
set up howl to sit on top of a JDBC database, but I found the details
hidden in the default config.
You can have howl journal to disk and then periodically dump its
journals to a database in a batch, which was the behaviour I was expecting.
<journaledJDBC journalLogFiles="5" dataDirectory="../activemq-data"
dataSource="#postgres-ds"/>
Not exactly. The journaled JDBC does not use howl.
Howl must be configured on the transaction manager and is not related to
ActiveMQ directly. It will only log xa transactions data, whereas the ActiveMQ
journal will hold jms messages enlisted in a transaction.
Take a look at the tx.xml file in the conf directory of
servicemix distribution. If i recall, there is a commented snippet that
you can use to configure howl.
Terry
--
Cheers,
Guillaume Nodet
