Hello,
I have an ActiveMQ broker running as a Windows service. Its using
jdbcPersistenceAdapter with Oracle data source and Oracle's Universal
Connection Pooling (UCP).
When the database is down (due to network problems or scheduled
maintenance), the ActiveMQ windows service shuts down completely. This, of
course makes the broker unavailable even after the database is restored.
I have tried connection validation in UCP, DBCP with connection validation
and even MySQL data source without any success. The service shuts down
within 30 seconds of database failure (persistenceAdapter cleanupInterval is
using the default value of 30 seconds).
Is there a way to prevent the windows service from shutting down and make it
wait for database availability? Any help is greatly appreciated.
Here is my current configuration from activemq.xml:
<persistenceAdapter>
<jdbcPersistenceAdapter dataSource="#oracle-ds"/>
</persistenceAdapter>
<bean id="oracle-ds" class="oracle.ucp.jdbc.PoolDataSourceFactory"
factory-method="getPoolDataSource"
p:URL="jdbc:oracle:thin:@localhost:1521:amq"
p:connectionFactoryClassName="oracle.jdbc.pool.OracleDataSource"
p:validateConnectionOnBorrow="true" p:user="appuser"
p:password="userspassword" />
--
View this message in context:
http://activemq.2283324.n4.nabble.com/ActiveMQ-windows-service-using-JDBC-persistence-tp4385895p4385895.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
