activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <christian.po...@gmail.com>
Subject Re: Retry connection on broker start when database is unavailable
Date Tue, 18 Jun 2013 19:35:32 GMT
Can you give a try to one of the nightly snapshots? This should be resolved
in 5.9:

https://issues.apache.org/jira/browse/AMQ-4526



On Tue, Jun 18, 2013 at 2:01 PM, afant <allenfant@gmail.com> wrote:

> I am using ActiveMQ 5.7  with JDBC master/slave (mySQL) configuration.
> Additionally, I have configured HA to use jdbcPersistenceAdapter that uses
> the the database locker by default.  Currently, by design the broker will
> not start unless the broker can connect to the database.  If the broker is
> started before the database is started, I get the following Runtime
> exception, ERROR failed to start Apache ActiveMQ. Reason:
> java.io.IOException: Communication link failure.
>
> Our project routinely does patch upgrades to it's servers, and we have no
> control over the order in which our ActiveMQ brokers and mysql databases
> (jdbcPersistenceAdapters) are started.  The desired behavior would be to
> start the broker (no RuntimeException), and allow the broker to retry
> (multiple times) the connection to the database.  Is this feature available
> in this release?  If so, could you provide me with the documentation to set
> this up?
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Retry-connection-on-broker-start-when-database-is-unavailable-tp4668329.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>



-- 
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message