Hello. Does anyone know if there is logic in activeMQ to retry connecting to a database if JDBC master/slave is configured? Perhaps there is some configuration I'm missing. Right now we log ship from the active Sql Server database to the passive Sql Server database. During maintenance it would be nice to fail to the passive database without impacting the ActiveMQ broker and requiring a restart. When I tested I just stopped the sql server windows service and the active ActiveMQ broker shut down requiring a manual startup.
Current JDBC master/slave configuration snippets: <persistenceAdapter> <jdbcPersistenceAdapter dataSource="#mssql-ds"/> </persistenceAdapter> ... <bean id="mssql-ds" class="org.apache.commons.dbcp.BasicDataSource" destroy-method="close"> <property name="driverClassName" value="com.microsoft.sqlserver.jdbc.SQLServerDriver"/> <property name="url" value="jdbc:sqlserver://QG076619.qg.com:1433;databaseName=activedb;user=sa;password=pa$$word"/> <property name="username" value="activemq"/> <property name="password" value="pa$$word"/> </bean> -- View this message in context: http://www.nabble.com/Is-there-JDBC-master-slave-retry-logic-if-database-goes-down--tp22440338p22440338.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
