2 Replies Latest reply: Jun 11, 2012 3:53 AM by 840361 RSS

    ojdbc6 failover connection timeout

    840361

      Hi,
      We have two oracle 10g physical servers running, all our web services use OLTP service which always points to server1 in case of failures service will relocate to server2.
      And we have two JBoss services calling this OLTP service with failover definition on in driver signature.

      JBoss-1 service successfully failed over to second node and successfully functioning.
      But JBoss-2 service transactions were timingout. We have driver signature same in both services but with some other below differences

      The potential difference I could see is ojdbc jar version - would this problem solve if we upgrade/downgrade this jar in JBoss-2?


      JBoss-1 OS:
      Red Hat 3.4.6-9

      JBoss-1 Java version
      java version "1.5.0_16"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02)
      Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_16-b02, mixed mode)

      JBoss-1 JBosss version:
      jboss-4.0.5.GA

      JBoss-1 uses OJdbc4.jar:


      JBoss-2 OS:
      Red Hat Enterprise Linux Server release 5.4

      JBoss-2 Java version
      java version "1.6.0_17"
      Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
      Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01, mixed mode)

      JBoss-2 JBosss version:
      JBoss-eap-5.0

      JBoss-2 OJdbc6.jar:
      Oracle JDBC Driver version - "11.1.0.7.0-Production"

      JBoss-1 and 2 oracle-ds.xml:

      <local-tx-datasource>
      <jndi-name>PRDBOracleDS</jndi-name>
      <connection-url>jdbc:oracle:thin:@(DESCRIPTION =(ADDRESS =(PROTOCOL = TCP)(HOST = server486.us.dnb.com)(PORT = 1521))(ADDRESS = (PROTOCOL = TCP)(HOST = server487.us.dnb.com)(PORT = 1521))(LOAD_BALANCE = OFF)(FAILOVER = ON)(CONNECT_DATA =(SERVER = DEDICATED)(SERVICE_NAME = oltp_service)(FAILOVER_MODE =(TYPE = SELECT)(METHOD = BASIC)(RETRIES = 180)(DELAY = 5))))</connection-url>
      <driver-class>oracle.jdbc.driver.OracleDriver</driver-class>
      <user-name>user</user-name>
      <password>user123</password>
      <exception-sorter-class-name>org.jboss.resource.adapter.jdbc.vendor.OracleExceptionSorter</exception-sorter-class-name>
      <metadata>
      <type-mapping>ORACLE10G</type-mapping>
      </metadata>
      <min-pool-size>5</min-pool-size>
      <max-pool-size>50</max-pool-size>
      </local-tx-datasource>

      Edited by: 837358 on 08-Jun-2012 09:09

        • 1. Re: ojdbc6 failover connection timeout
          rp0428
          >
          The potential difference I could see is ojdbc jar version - would this problem solve if we upgrade/downgrade this jar in JBoss-2?
          >
          You should first test if JBOSS-2 can successfully failover.

          The test you performed was with both JBoss services running and you found that service #1 failed over but service #2 did not.l

          So shutdown service #1, leave service #2 running and test the failover. Either service #2 will fail over or the system will die.

          If service #2 fails over then you can run out the ojdbc jar version being an issue. If service #2 doesn't fail over then you should just leave service #1 offline while you research and resolve the problem with service #2.
          • 2. Re: ojdbc6 failover connection timeout
            840361
            Thanks rp0428.
            I would definitely want to try what you have suggested. But the problem we are facing is on production systems. We couldn't replicate this issue in lower environments because we don't have RAC set up. We have got only one server running in lower env.
            So I posted here to know if this is already known problem.