activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <>
Subject [jira] [Resolved] (AMQ-1780) ActiveMQ broker does not automatically reconnect if the connection to the database is lost
Date Mon, 28 Mar 2011 11:10:06 GMT


Gary Tully resolved AMQ-1780.

       Resolution: Fixed
    Fix Version/s:     (was: NEEDS_REVIEWED)
         Assignee: Gary Tully

reused the plug-able [IOExceptionHandler|].
It is now called when a call to JDBC getConnection fails. Extended the DefaultIOExceptionHandler
to allow stop/resume of connectors option rather than simple broker stop. Added Xbean support
for DefaultIOExceptionHandler so it can be easily included in xml configuration.

Relevant programatic configuration from the test, use stopStartConnectors and do not ignore
sql exceptions. Disable the default DB lock such that it will not stop the broker on a lock
failure.{code}        DefaultIOExceptionHandler handler = new DefaultIOExceptionHandler();
        JDBCPersistenceAdapter persistenceAdapter = new JDBCPersistenceAdapter();

> ActiveMQ broker does not automatically reconnect if the connection to the database is
> ------------------------------------------------------------------------------------------
>                 Key: AMQ-1780
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.0.0
>         Environment: Windows 2003 Server
>            Reporter: Jaya Srinivasan
>            Assignee: Gary Tully
>             Fix For: 5.5.0
> hi
> We are noticing that after any SQL Server restart or network blip between ActiveMQ and
the database, after the connection or the database comes back online activeMQ broker needs
to be restarted as well i.e it doesn't automatically re-establish connection to the database
as result any message send fails because the broker is still using the stale connection to
the database. 
> Is this designed behaviour or a bug? we are using ActiveMQ 5.0.0 and the latest version
of the JSQLConnect database driver: version 5.7. The database we are using is MS SQL Server
> Right now, in our production environment any time we have network maintenance or database
restart we also have to restart the ActiveMQ broker which is not a good option for us. 
> Also, We are using a single ActiveMQ broker and not the JDBC(Master/Slave) set up.
> Issue details in
> Please let me know if I need to give more information
> thanks
> jaya

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message