This discussion is archived
2 Replies Latest reply: Dec 21, 2012 1:52 AM by 981006 RSS

FAIL_OVER in jdbc url

981006 Newbie
Currently Being Moderated

Recently one of db database node was down and our application did not connect to another node as per the below URL because we have configured FAIL_OVER=ON.


Can any one explain why fail over did not happen. We are using Oracle 10g and RHEL 5.3 OS.

  • 1. Re: FAIL_OVER in jdbc url
    jschellSomeoneStoleMyAlias Expert
    Currently Being Moderated
    How do you know it didn't happen?

    Explain in detail what you saw, what you expected, and how long the condition lasted.
  • 2. Re: FAIL_OVER in jdbc url
    981006 Newbie
    Currently Being Moderated

    Due to Hardware failure one of the node was down. We expected our application to connect to another node which was up and running, but did not happen. It lasted for almost 1 hour. Once the node went down i could see only below exception in jboss server logs.

    Initially i got below WARN messages :

    2012-12-17 15:00:44,196 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id 619289df:dc67:50ce06ae:6bd9 invoked while multiple threads active within it.
    2012-12-17 15:00:44,196 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action 619289df:dc67:50ce06ae:6bd9 aborting with 1 threads active!
    2012-12-17 15:00:44,760 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.BasicAction_58] - Abort of action id 619289df:dc67:50ce06ae:6bda invoked while multiple threads active within it.
    2012-12-17 15:00:44,760 WARN [com.arjuna.ats.arjuna.logging.arjLoggerI18N] [com.arjuna.ats.arjuna.coordinator.CheckedAction_2] - CheckedAction::check - atomic action 619289df:dc67:50ce06ae:6bda aborting with 1 threads active!

    Later after minutes i found below Exceptions

    2012-12-17 15:04:04,218 WARN [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Throwable while attempting to get a new connection: null
    org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (java.sql.SQLException: Io exception: Connection reset)
    at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(
    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(
    at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(
    at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(
    at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(
    at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(
    at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(
    at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(
    at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(

    Any idea about the Warning messages we received.



  • Correct Answers - 10 points
  • Helpful Answers - 5 points