Hi Tim,
Thank you for your assistance and your quick response.
As for the questions, let me try to explain better:
1. We have 2 ActiveMQ Services installed (A, B) on different machines (Amq1,
Amq2)
which are configured in ActiveMQ Failover configuration-
Both relay on a single SQL database
Of course it fails, but it should not put the service down.
The service should keep running until it can reconnect.
I believe this is not a normal behavior of ActiveMQ,
and if it is, how can I config it otherwise?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Crushing-
This is what I get in the log files when it happens:
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JDBC-driver-with-Failover-Master-Slave-MS-SQL-database-tp4702654p4703112.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
How can I report this as a bug?
--
View this message in context:
http://activemq.2283324.n4.nabble.com/JDBC-driver-with-Failover-Master-Slave-MS-SQL-database-tp4702654p4703098.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi,
I set an ActiveMQ service based on database using JDBC to a Failover MS SQL
Server Database.
When the SQL server fails-over, the AMQ service goes down for some reason,
and doesn't go up back again.
How can I prevent it?
Do I need to configure anything?
I'm using version 1.11.1
***
Here's w
