activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kiorsak (JIRA)" <>
Subject [jira] [Commented] (AMQ-1780) ActiveMQ broker does not automatically reconnect if the connection to the database is lost
Date Thu, 07 Apr 2011 04:28:06 GMT


Oleg Kiorsak commented on AMQ-1780:

there is an issue however... 

when the database is stopped for very small period of time - everything works somewhat rather
smoothly and as expected... but once DB is not available for longer time (5 secs)

" INFO | waiting for broker persistence adapter checkpoint to succeed before restarting transports"


"INFO | Connector openwire Stopped"

so far so good - makes sense (but note that it only stooped "openwire" one at this point,

but when I restart the database, it then goes and stops (!!) the other transport connectors
(in particular STOMP one), but does not start them back...

INFO | Connector STOMP Stopped
 INFO | Connector xmpp Stopped

only when I go to jConsole and _manually_ start the STOMP transport connector (one we're using)
things get back to normal...

 INFO | Listening for connections at: stomp://mdtapdot01:10002
 INFO | Connector STOMP Started

but that means it requires a manual procedure....

it seems to me this is a bug and in fact it was meant to actually "restart transports", not
just stop them...

it might be that there is in fact a different handling of "openwire" and the other s ("STOMP")
connectors... (based on the fact that "openwire" stops when DB connection detected as lost,
but "STOMP" gets stopped when DB is restored... and does not get restarted automatically...


> 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