gain a lock on the
DB. Now we have a problem of two instances of ActiveMQ are running.
Any advice on the best method?
--
View this message in context:
http://old.nabble.com/Noob-Questions---Fail-over---Redundancy-Help.-tp29057308p29216328.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
nvironment that mimics your
> production environment first. You may have to use trial and error to find
> the right settings for your OS and data store.
>
>
--
View this message in context:
http://old.nabble.com/Noob-Questions---Fail-over---Redundancy-Help.-tp29057308p29090904.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
lar intervals set by
sqlnet.expire_time (in minutes!).
As always, do your testing in an environment that mimics your production
environment first. You may have to use trial and error to find the right
settings for your OS and data store.
--
View this message in context:
http://old.nabble.com/Noob-Q
gt;
> Any advice?
>
> What's the best option for prompt fail-over for my mission critical
> application. Downtime not exceeding 6 minutes a year is the expectation to
> meet.
>
> Thanks!
>
--
View this message in context:
http://old.nabble.com/Noob-Questions---Fail-over---Redundancy-Help.-tp29057308p29066738.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
View this message in context:
http://old.nabble.com/Noob-Questions---Fail-over---Redundancy-Help.-tp29057308p29057308.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
