This question was posted May 16, 2011; 11:18am — by johanhonline johanh but I cannot locate any follow-up or resolution.
Currently (04/25/2017) we have the same issue and I need to understand how to integrate Active MQ with Oracle 12.1.0.2 TAF (Transparent Application Failover) so that bouncing one node of the Oracle RAC doesn't break Active MQ as described in the original post below. I have read and understand the Oracle TAF documentation and combed through Active MQ lists. Just need some input on how to get Active MQ to integrate with Oracle TAF. Any pointers to manuals/documentation or resources describing tests (successful or not) to get Active MQ to work with Oracle TAF are appreciated. Thanks -- bsm...@skylinenet.net johanh wrote > Hi list, > > We are currently running a master-slave cluster of ActiveMQ nodes, with a > JDBC persistence adapter backed by an Oracle 11g RAC database. This is > working fine from an ActiveMQ perspective; when the master goes down, a > slave automatically becomes the new master. However, we are having issues > when one of the database nodes goes down, and I am looking for ways to > have the ActiveMQ nodes handle this event as seamlessly as possible: > <snipped... Oracle TAF configuration...> > When one of the database nodes goes down, the master ActiveMQ node loses > its database lock, with the database returning an "ORA-25402: transaction > must roll back error". Per our DBA, this is normal behavior for Oracle > RAC, and is the Oracle OCI JDBC driver's cue to retry the connect. > However, this error causes the master ActiveMQ node to shut down entirely: > <snipped..> > After this, the earlier master node is completely shut down (the process > is no longer running), and none of the earlier slave nodes have taken over > as master. Restarting the master node ActiveMQ service makes it reacquire > the lock and become master again. Comparing these observations to what we > see in the database, it seems that the OCI driver is attempting to fail > over the connection to another database node (we can see some connections > from it failing over), but apparently that process gets interrupted by the > ActiveMQ master node shutting down per the above. Is there some way in > ActiveMQ to have the master node either attempt to reacquire the lock > itself, or wait for some time before shutting down, or is there some other > way in which database transparent application failover has been > implemented in ActiveMQ? > > Any advice appreciated! > > Regards, > Johan H -- View this message in context: http://activemq.2283324.n4.nabble.com/Can-ActiveMQ-take-advantage-of-Oracle-transparent-application-failover-tp3526485p4725226.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
