-
Bug
-
Resolution: Done
-
Major
-
None
-
None
There is a needed workaround for setting up JDBC adapter in activemq.xml in order to make connection work "out of the box".
2019-08-12 14:22:24,956 | INFO | AMQ-1-thread-1 | JDBCPersistenceAdapter | tore.jdbc.JDBCPersistenceAdapter 478 | 162 - org.apache.activemq.activemq-osgi - 5.11.0.redhat-630403 | Database adapter driver override not found for : [microsoft_jdbc_driver_6_4_for_sql_server]. Will use default implementation.
One has to perform following updates (commented out):
<bean class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close" id="jdbc-ds"> <property name="driverClassName" value="com.microsoft.sqlserver.jdbc.SQLServerDriver"/> <property name="url" value="jdbc:sqlserver://URL"/> <property name="username" value="username"/> <property name="password" value="password"/> <property name="maxActive" value="200"/> <property name="poolPreparedStatements" value="true"/> </bean> <!-- <bean id="MSSQLAdapter" class="org.apache.activemq.store.jdbc.adapter.TransactJDBCAdapter"/> --> <broker xmlns="http://activemq.apache.org/schema/core" brokerName="${broker-name}" dataDirectory="${data}" restartAllowed="false" start="false"> <persistenceAdapter> <jdbcPersistenceAdapter dataDirectory="${data}" dataSource="#jdbc-ds"/> <!-- adapter="#MSSQLAdapter"/> --> </persistenceAdapter> ...
- is cloned by
-
ENTMQ-2323 PostgreSQL 9.3/9.4 setup workaround needed to define Adapter
- Closed
- is related to
-
ENTMQBR-2684 Automate DBs jobs for AMQ 6
- Closed