Using the JDBC persistence adapter with Fuse MQ Enterprise's high performance journal boosts the performance of the persistence adapter in two ways:

In addition to the performance gains, the high performance journal also makes it possible to ensure the consistency of JMS transactions in the case of a system failure.

	Warning
	The journaled JDBC store is incompatible with the JDBC master/slave failover pattern—see Shared JDBC Master/Slave in Fault Tolerant Messaging

Before you can use the journaled JDBC persistence store you need to ensure that the activeio-core-3.1.4.jar bundle is installed in the container.

The bundle is available in the archived ActiveMQ installation included in the InstallDir/extras folder, or you can download it from Maven at http://mvnrepository.com/artifact/org.apache.activemq/activeio-core/3.1.4.

Example 8 shows a configuration fragment that configures the journaled JDBC adapter to use a MySQL database.

<beans ... >
  <broker ...>
    ...
  <persistenceFactory>
    <journalPersistenceAdapterFactory journalLogFiles="5" dataDirectory="${data}/kahadb"
			    dataSource="#mysql-ds" useDatabaseLock="true"
			    useDedicatedTaskRunner="false" />
    </persistenceFactory>
    ...
  <broker>
  ...
<bean id="mysql-ds"
      class="org.apache.commons.dbcp.BasicDataSource"
      destroy-method="close">
    <property name="driverClassName" value="com.mysql.jdbc.Driver"/>
    <property name="url" value="jdbc:mysql://localhost/activemq?relaxAutoCommit=true"/>
    <property name="username" value="activemq"/>
    <property name="password" value="activemq"/>
    <property name="poolPreparedStatements" value="true"/>
  </bean>

The configuration in Example 8 has three noteworthy elements:

Table 3 describes the attributes used to configure the journaled JDBC persistence adapter.