Hi,
We are running activemq 5.5.1 in an active/passive failover configuration with
JDBC Persistence to an Oracle backend. The default strategy for determining
whether the current master has failed is for the secondary server to attempt to
get a lock on the database table, waiting indefinitely for the lock to be granted.
This is not working (at least in our context) as, after a relatively short time
in operation (a handful of hours at most) the connection to Oracle is dropped.
Activemq doesn't notice this, so the secondary sits there happily waiting for a
lock it can now never get and, in the event of a failure, won't serve any
clients as it is not a master.
Is there some way to change the decision mechanism to, eg, a polling strategy?
Or can anyone suggest another resolution to this problem?
Alex.
--
Alex Hooper
Operations Team Leader, BMJ Group, BMA House, London WC1H 9JR
Tel: +44 (0) 20 7383 6049
http://group.bmj.com/
_______________________________________________________________________
The BMJ Group is one of the world's most trusted providers of medical
information for doctors, researchers, health care workers and patients
group.bmj.com. This email and any attachments are confidential. If you have
received this email in error, please delete it and kindly notify us. If the
email contains personal views then the BMJ Group accepts no responsibility for
these statements. The recipient should check this email and attachments for
viruses because the BMJ Group accepts no liability for any damage caused by
viruses. Emails sent or received by the BMJ Group may be monitored for size,
traffic, distribution and content. BMJ Publishing Group Limited trading as BMJ
Group. A private limited company, registered in England and Wales under
registration number 03102371. Registered office: BMA House, Tavistock Square,
London WC1H 9JR, UK.
_______________________________________________________________________
