My last question in that three-year-old thread applies to you too: are you
using a wrapper such as Tanuki that would detect the broker process exiting
and respond by restarting the ActiveMQ process? This would be the expected
way to handle this situation, so if you're not doing that, it's what I'd
I have the same issue with ActiveMQ. I have two nodes of AMQ and it is
configured to use MS SQL with database cluster. When the database cluster
fails over, my AMQ stops working and I need to re-start it manually to fix
the issue. Could you please post how did you fix your issue?
--
Sent from: h
Thanks for clarifying about the behavior when manually restart the broker
after a failover.
Are you using Tanuki's ability to restart a process automatically? If so,
does Tanuki retry repeatedly while the database is in the process of
failing over?
On Nov 2, 2015 7:39 AM, "Abrasha70" wrote:
> H
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
This is normal and expected behavior for ActiveMQ with KahaDB as well.
I've never used LevelDB, so I can't speak to its behavior, though I have no
reason to believe it would behave differently than the other two.
ActiveMQ can't work without a backing store if you've configured it to
require one.
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-
So the logs pretty clearly say that the broker shut down because the broker
lost the JDBC lock (because it couldn't talk to the database) and that it
failed to restart a little later because it still couldn't talk to the
database.
When the database has failed over and ActiveMQ fails to reconnect,
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.
Bug reports get submitted in JIRA:
https://issues.apache.org/jira/browse/AMQ/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel
With that being said, your original description said that "the AMQ service
goes down for some reason". I've never seen ActiveMQ go down without
logging, o
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.
10 matches
Mail list logo
