JDBC - Fail over connection

Hello Group,
I ´m currently working on the follwing szenario in XI (NW2004, SP19):
Via the jdbc adapter I send a sql statement to a database (db1) and get the response. This works fine.
Because it´s a very important request, I have a second database (db2) with exactly the same data as in db1. When the db1 is not reachable, the adapter should connect automatically the db2.
Can I handle this with the jdbc adapter (fail over connection)? Or with another configuration in the XI.
Thanks in advance.
Kind regards,
Martin

hi
you can use a bpm with an exception brach where you specify if first db fail try to connect to db2
it a useful solution

Similar Messages

JDBC fails to connect to 8.1.7.0.1 on Linux

Hi,
I compile and run the sample JDBCVersion program on a Win98 client PC. It works ok connecting to a Sparc 8.1.7.0.1. However, when it connects to 8.1.7.0.1 on Redhat 7.3, it gives the following error.
D:\Programs>java JDBCVersion
Exception in thread "main" java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:169)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:211)
at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:324)
at oracle.jdbc.driver.OracleConnection.<init>(OracleConnection.java:266)
at oracle.jdbc.driver.OracleDriver.getConnectionInstance(OracleDriver.java:365)
at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:260)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at JDBCVersion.main(jdbcversion.java:10)
The strange thing is if the same program is run on the local Redhat 7.3 machine, it works fine!
I checked the listener.log file. The log message for the successful and unsuccessful cases are the same (of course except the HOST= field).
Is it a bug?
Regards,
John Lee

Hi Rahul,
Thanks for your response. I'm using Oracle Java Thin client. Environment is J2SE SDK 1.4.1_01 (uses classes12.zip from Oracle).
Successful cases
- Win98 can use ODBC and SQL*PLUS to connect to the remote Oracle8i
- Win98 can use JDBCVersion program to connect to a remote Oracle8i on Sparc and another Oracle9i on RedHat 7.3
- JDBCVersion can successfully connects to Oracle8i on Redhat 7.3 if it is run locally on the database server
Failed cases
- When JDBCVersion runs on Win98, it fails to connect to remote Oracle8i on Redhat 7.3
The log from listener.log shows that nothing special happens when JDBCVersion runs on Win98 to connect.
Any clues?
Regards,
John

Failing over Oracle connections in a pool

          Hi,
          This message is probably a bit out of context (I've already posted
          it to the JDBC group). I post here as well, since I guess it's
          the place where people have the most experience with clustering
          and HA. Original posting below...
          Could you please tell me whether, yes or no, connections to an
          Oracle database should fail over (when the database fails over
          to another machine)? I use Oracle's Transparent Application Failover
          (configured via Net8) with Weblogic 6 on Linux and Oracle 8.1.7
          on Solaris/SPARC.
          If this doesn't work in my configuration, is there any configuration
          where it should work? (Another version of Oracle, WLS, OS, ...)
          When I try TAF using the PetStore application, I get exceptions
          related to no being connected to the database.
          If TAF doesn't work with WebLogic, is there a way to work around
          the problem? Can I catch these exceptions and renew the connections
          in the pool? Or, what else is possible...?
          I'd appreciate any help. I'd like to demonstrate our HA product
          with WLS. If it doesn't work, I'll turn to iPlanet instead. Pity,
          I really like WLS!
          Thanks in advance for any help or advice!
          Regards, Frank Olsen


          Hi (Frank ;-)
          I got carried away a bit too fast...
          Some more testing shows that it doesn't work in all cases:
          - when someone is trying to check out the shopping cart when the
          the database fails (and fails over), I get exceptions once the
          databses has restarted on the backup node
          - the exceptions are related to some transactions being rolled
          back and Oracle stating that it couldn't safely replay the transactions
          - browsing the categories still works fine
          - all access to the shopping cart and sign-in/sign-out causes time-outs
          and exceptions
          Any ideas what may cause this problem, please?
          Regards,
          Frank Olsen
          "Frank Olsen" <[email protected]> wrote:
          >
          >Hi,
          >
          >TAF worked with WLS 6 on NT with the Oracle 8.1.7 client!
          >
          >Has anyone tested it on Solaris/SPARC?
          >
          >Regards,
          >Frank Olsen
          >
          >
          >
          >"Frank Olsen" <[email protected]> wrote:
          >>
          >>Hi,
          >>
          >>Most of my question below is still valid (in particular
          >>concerning
          >>whether TAF should work with WLS on some or all platforms
          >>and
          >>versions).
          >>
          >>However, when I tested TAF with the Oracle client (sqlplus)
          >>there
          >>also was no failover of the (one) connection. I then
          >checked
          >>the
          >>`V$SESSION' view and the colums related to failover showed
          >>that
          >>TAF was not correctly configured. Strange because I copied
          >>the
          >>`tnsnames.ora' parameters from the Oracle documentation
          >>for TAF.
          >>
          >>Has anyone managed to configure and use TAF, with or
          >without
          >>WLS?!
          >>
          >>Thanks in advance for your help!
          >>
          >>Regards,
          >>Frank Olsen
          >>
          >>
          >>"Frank Olsen" <[email protected]> wrote:
          >>>
          >>>Hi,
          >>>
          >>>This message is probably a bit out of context (I've
          >already
          >>>posted
          >>>it to the JDBC group). I post here as well, since I
          >guess
          >>>it's
          >>>the place where people have the most experience with
          >>clustering
          >>>and HA. Original posting below...
          >>>
          >>>----
          >>>
          >>>Could you please tell me whether, yes or no, connections
          >>>to an
          >>>Oracle database should fail over (when the database
          >fails
          >>>over
          >>>to another machine)? I use Oracle's Transparent Application
          >>>Failover
          >>>(configured via Net8) with Weblogic 6 on Linux and Oracle
          >>>8.1.7
          >>>on Solaris/SPARC.
          >>>
          >>>If this doesn't work in my configuration, is there any
          >>>configuration
          >>>where it should work? (Another version of Oracle,
          >WLS,
          >>>OS, ...)
          >>>
          >>>
          >>>When I try TAF using the PetStore application, I get
          >>exceptions
          >>>related to no being connected to the database.
          >>>
          >>>If TAF doesn't work with WebLogic, is there a way to
          >>work
          >>>around
          >>>the problem? Can I catch these exceptions and renew
          >the
          >>>connections
          >>>in the pool? Or, what else is possible...?
          >>>
          >>>I'd appreciate any help. I'd like to demonstrate our
          >>HA
          >>>product
          >>>with WLS. If it doesn't work, I'll turn to iPlanet instead.
          >>>Pity,
          >>>I really like WLS!
          >>>
          >>>Thanks in advance for any help or advice!
          >>>
          >>>Regards, Frank Olsen
          >>>
          >>
          >

How do the application servers connect the new database after failing over from primary DB to standby DB

How do the application servers connect the new database after failing over from primary DB to standby DB?
We have setup a DR environment with a standalone Primary server and a standalone Physical Standby server on RHEL Linux 6.4. Now our application team would like to know:
When the primary DB server is crashed, the standy DB server will takeover the role of primary DB through the DataGuard fast failover. As the applications are connected by the primary DB IP before,currently the physical DB is used as a different IP or listener. If this is happened, they need to stop their application servers and re-configure their connection so the they coonect the new DB server, they cannot tolerate these workaround.
Whether does oracle have the better solution for this so that the application can automatically know the role's transition and change to the new IP without re-confige any connection and shutdown their application?
Oracle support provides us the answer as following:
==================================================================
Applications connected to a primary database can transparently failover to the new primary database upon an Oracle Data Guard role transition. Integration with Fast Application Notification (FAN) provides fast failover for integrated clients.
After a failover, the broker publishes Fast Application Notification (FAN) events. These FAN events can be used in the following ways:
Applications can use FAN without programmatic changes if they use one of these Oracle integrated database clients: Oracle Database JDBC, Oracle Database Oracle Call Interface (OCI), and Oracle Data Provider for .NET ( ODP.NET). These clients can be configured for Fast Connection Failover (FCF) to automatically connect to a new primary database after a failover.
JAVA applications can use FAN programmatically by using the JDBC FAN application programming interface to subscribe to FAN events and to execute event handling actions upon the receipt of an event.
FAN server-side callouts can be configured on the database tier.
FAN events are published using Oracle Notification Services (ONS) and Oracle Streams Advanced Queuing (AQ).
=======================================================================================
Who has the experience and the related documentation or other solutions? we don't have the concept of about FAN.
Thank very much in advance.

Hi mesbeg,
Thanks alot.
For example, there is an application JBOSS server connecting the DB, we just added another datasource and put the standby IP into the configuration file except adding a service on DB side like this following:
        <subsystem xmlns="urn:jboss:domain:datasources:1.0">
        <datasources>
                <datasource jta="false" jndi-name="java:/jdbc/idserverDatasource" pool-name="IDServerDataSource" enabled="true" use-java-context="true">
                    <connection-url>jdbc:oracle:thin:@<primay DB IP>:1521:testdb</connection-url>
                    <connection-url>jdbc:oracle:thin:@<standby DB IP>:1521:testdb</connection-url>
                    <driver>oracle</driver>
                    <pool>
                        <min-pool-size>2</min-pool-size>
                        <max-pool-size>10</max-pool-size>
                        <prefill>true</prefill>
                    </pool>
                    <security>
                        <user-name>TEST_USER</user-name>
                        <password>Password1</password>
                    </security>
                    <validation>
                        <valid-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleValidConnectionChecker"/>
                        <validate-on-match>false</validate-on-match>
                        <background-validation>false</background-validation>
                        <use-fast-fail>false</use-fast-fail>
                        <stale-connection-checker class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleStaleConnectionChecker"/>
                        <exception-sorter class-name="org.jboss.jca.adapters.jdbc.extensions.oracle.OracleExceptionSorter"/>
                    </validation>
                </datasource>
                <drivers>
                    <driver name="oracle" module="com.oracle.jdbc">
                        <xa-datasource-class>oracle.jdbc.OracleDriver</xa-datasource-class>
                    </driver>
                </drivers>
            </datasources>
        </subsystem>
If the failover is occurred, the JBOSS will automatically be pointed to the standby DB. Additional actions are not needed.

Thin Client connection not failing over

I'm using the following thin client connection and the sessions do not failover. Test with SQLPLUS and the sessions do fail over. One difference I see between the two different connections is the thin connection has NONE for the failover_method and failover_type but the SQLPLUS connection show BASIC for failover_method and SELECT for failover_type.
Is there any issues with the thin client the version is 10.2.0.3
jdbc:oracle:thin:@(description=(address_list=(load_balance=YES)(address=(protocol=tcp)(host=crpu306-vip.wm.com)(port=1521))(address=(protocol=tcp)(host=crpu307-vip.wm.com)(port=1521)))(connect_data=(service_name=ocsqat02)(failover_mode=(type=select)(method=basic)(DELAY=5)(RETRIES=180))))

You have to use (FAILOVER=on) as well on jdbc url.
http://download.oracle.com/docs/cd/B19306_01/network.102/b14212/advcfg.htm#sthref1292
Example: TAF with Connect-Time Failover and Client Load Balancing
Implement TAF with connect-time failover and client load balancing for multiple addresses. In the following example, Oracle Net connects randomly to one of the protocol addresses on sales1-server or sales2-server. If the instance fails after the connection, the TAF application fails over to the other node's listener, reserving any SELECT statements in progress.sales.us.acme.com=
(DESCRIPTION=
*(LOAD_BALANCE=on)*
*(FAILOVER=on)*
(ADDRESS=
(PROTOCOL=tcp)
(HOST=sales1-server)
(PORT=1521))
(ADDRESS=
(PROTOCOL=tcp)
(HOST=sales2-server)
(PORT=1521))
(CONNECT_DATA=
(SERVICE_NAME=sales.us.acme.com)
*(FAILOVER_MODE=*
*(TYPE=select)*
*(METHOD=basic))))*
Example: TAF Retrying a Connection
TAF also provides the ability to automatically retry connecting if the first connection attempt fails with the RETRIES and DELAY parameters. In the following example, Oracle Net tries to reconnect to the listener on sales1-server. If the failover connection fails, Oracle Net waits 15 seconds before trying to reconnect again. Oracle Net attempts to reconnect up to 20 times.sales.us.acme.com=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=tcp)
(HOST=sales1-server)
(PORT=1521))
(CONNECT_DATA=
(SERVICE_NAME=sales.us.acme.com)
*(FAILOVER_MODE=*
*(TYPE=select)*
*(METHOD=basic)*
*(RETRIES=20)*
*(DELAY=15))))*

Connection Fail-over

My database may be replicated to multiple servers, in the event that a connection fails to the primary server, my class should try the same statement on the next context in an ordered list.
Any advice on errors to watch for to know the connection is broken (versus an error resulting from the query itself)?
Any advice on executing a query for one connection, and then if it fails, executing the same statement on a different connection? I am hoping to keep the fail-over logic encapsulated in a simple to use class so that all the classes that call stored procedures don't have to contain the logic.
I primarily use stored procedures, but have an occasional text sql query too.
Many thanks in advance!
Darcy

the best way to test this would probably be to establish a connection to the database, and then stop the database and try to execute a query against it and see what SQLException gets thrown, then you can watch for that one.
also, if you are using database pooling (or even if you aren't) you can validate each connection object you create with something like "select getDate()" or something basic that should return at least one row. if you don't get a row back or if you get an exception you know something is wrong with the database and you can then move to the next one.

Unity Connection 10.5(1)SU1a Publisher/Subscriber failing over

Recently upgraded to Unity Connection version: 10.5.1ES78.11901-78 from 9.1.2ES46.12900-46.
After upgrading we are experiencing an issue whereby the pub continually fails over to the sub without any obvious reason for the fail over. We've experienced this bug before on 9.1.1 which was the reason for the upgrade to 9.1.2. There is no bug case that is established for this issue on v10.5(1)SU1a. Pub is still taking calls in secondary state but obviously the need for stability between the nodes is necessary.
Anyone else experience or know of any issues on this most recently released version?
Thanks

To start with you can check if the replication is setup correctly and if any core dumps are being generated on the servers.
utils dbreplication runtimestate
utils core active list
HTH
Manish

Help : Cluster Fail over Test - Could not establish a connection

Hi All
          I'm trying to do Cluster fail over test with two Weblogic 8.1 sp2 instances in cluster.
          During that testing, I'm restarting the one of the instance which is handing my request, to make sure the session is replicated smoothly to the other instance,so that can continue accessing my application without any interuption. But when I restart the instance, I'm getting following exception
          Error 500--Internal Server Error
          java.rmi.ConnectException: Could not establish a connection with 8909815174098071019S:dappsn03:[8201,8201,-1,-1,8201,-1,-1,0,0]:dappsn03-04:TNL:tnl1_81dappsn03, java.rmi.ConnectException: Destination unreachable; nested exception is:
               java.net.ConnectException: Connection refused; No available router to destination
               at weblogic.rjvm.RJVMImpl.getOutputStream(RJVMImpl.java:316)
               at weblogic.rjvm.RJVMImpl.getRequestStream(RJVMImpl.java:488)
               at weblogic.rjvm.RJVMImpl.getOutboundRequest(RJVMImpl.java:584)
               at weblogic.rmi.internal.BasicRemoteRef.getOutboundRequest(BasicRemoteRef.java:91)
               at weblogic.rmi.internal.activation.ActivatableRemoteRef.invoke(ActivatableRemoteRef.java:69)
               at com.sns.pfk.ejb.PfkSessionBean_mz6mqm_EOImpl_812_WLStub.getPortalRecord(Unknown Source)
               at com.sns.pfk.servlet.PfkMainServlet.getInfofromSB(Unknown Source)
               at com.sns.pfk.servlet.PfkMainServlet.doActionDisplay(Unknown Source)
               at com.sns.pfk.servlet.PfkMainServlet.doGet(Unknown Source)
               at com.sns.pfk.servlet.PfkMainServlet.doPost(Unknown Source)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
               at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
               at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:607)
               at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:400)
               at com.sns.ana.ui.servlet.AuthorisationBaseServlet.service(AuthorisationBaseServlet.java:109)
               at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
               at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
               at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
               at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
               at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
               at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
               at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
               at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
               at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
          Buddies, anyone hit this issue before, pls show up some light to escape this hickup.
          With Regs
          -SHAN

Hi,
          Thanx for ones, spend time on reading this thread.This problem was due to some missing entries in weblogic-ejb.xml. This got fixed as we got support from BEA.
          With Regs
          -SHAN

BI JDBC Connection fails to connect to SQL Server 2000

Hello SDNs,
I have configured my JDBC connector to connect to MS SQL Server 2000(Third party in my case) using the document How to Configure UD connect on the J2EE server for JDBC Access to External Drivers.
I have given the following properties for my JDBC connector:
Driver Name : com.microsoft.jdbc.sqlserver.SQLServerDriver
URL : jdbc:microsoft:sqlserver://servername:1433;database=<databasename>
When i test the connection using the url: http://hostname:50000/TestJDBC_Web/TestJDBCPage.jsp
Here is the Error:
<b>Details:
com.sap.ip.bi.sdk.exception.BIConnectionFailedException: Cannot open the connection at com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcConnectionFactory.getConnectionEx(JdbcConnectionFactory.java:238) at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getConnection(JDBCModel.java:797) at com.sap.ip.bi.sdk.trialarea.connector.servlet.model.JDBCModel.getTables(JDBCModel.java:132) at
com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnection.(JdbcManagedConnection.java:118) ... 23 more Caused by: java.lang.ClassNotFoundException: com.microsoft.jdbc.sqlserver.SQLServerDriver Found in negative cache -
Loader Info -
ClassLoader name: [connector:default] Parent loader name: [Frame ClassLoader] References: common:service:http;service:servlet_jsp service:ejb common:service:iiop;service:naming;service:p4;service:ts service:jmsconnector library:jsse library:servlet common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl library:ejb20 library:j2eeca library:jms library:opensql common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore interface:resourcecontext_api interface:webservices interface:cross interface:ejbserialization common:library:bimmrcore;library:bimmrdb sap.com/cafcore sap.com/cafruntimeear library:tcconnconnectorframework library:sapxmltoolkit sap.com/com.sap.ip.bi.sdk.dac.connector.xmla.x library:com.sap.mw.jco library:com.sap.aii.proxy.framework library:com.sap.aii.util.misc library:com.sap.ip.bi.sdk.dac.connector.odbodll library:BI_JDBC library:bimmrcwm_1.0_library library:bimmrjmi library:com.sap.ip.bi.sdk library:MSSQL Resources: H:\usr\sap\BD2\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.ip.bi.sdk.dac.connector.xmla\connector\connectors\bi_sdk_xmla.rar\bi_sdk_xmla.jar H:\usr\sap\BD2\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\cafbwadapterassembly\connector\connectors\sap.com_cafbwadapterassembly.rar\lib\java\sap.comcafbwadapter~caf.bw.adapter.jar H:\usr\sap\BD2\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.ip.bi.sdk.dac.connector.sapq\connector\connectors\bi_sdk_sapq.rar\bi_sdk_sapq.jar H:\usr\sap\BD2\DVEBMGS00\j2ee\cluster\server0\apps\sap.com\com.sap.ip.bi.sdk.dac.connector.jdbc\connector\connectors\bi_sdk_jdbc.rar\bi_sdk_jdbc.jar Loading model: {parent,references,local} -
at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:360) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:141) at com.sap.ip.bi.sdk.dac.connector.jdbc.impl.Connection.connectDB(Connection.java:365) ... 25 more</b>
Please let me know if any changes are required in Driver name and URL.
Your inputs will be highly appreciated.
Thanks,
Sireesha.B
Message was edited by:
sireesha Borra

Hi Sireesha,
Some insights.....while using JDBC connector .
For JDK 1.1 environments, access to the "current working directory" mustbe granted.
For Java 2 environments, access to the temporary directory specified by the VM configuration must be granted. The following is an example of permissions being granted in the file java.security.policy for the C:\TEMP directory:
// permissions granted to all domains grant { // Permission to create and delete temporary files. // Adjust the temporary directory for your environment. permission java.io.FilePermission "C:
TEMP
-", "read,write,delete"; };
Note 777304 - Problems with JDBC drivers when using BI UDI
Related notes -
834385 - 'Invalid operation: result set closed' Exception
834384 - Problems with selection in InfoPackage in UD Connect
777306 - MSSQL problem when using BI UDI
777305 - Problems with Unicode when using BI UDI
Fyi-
http://dev.mysql.com/downloads/index.html
Regards,
Anil

Exception while failing over to 2nd RAC Node

We are using Weblogic 10.3.4. Our setup is that we have a Web Application (A tapestry front end Web UI) and EJb 2.1 back-end talking to the Oracle database. The EJB’s are CMP. Our product always was just stand alone and it wasn’t until this release we needed to make it work with RAC. To get this to work we followed the model of having a Multidatasource with datasources pointing to our RAC nodes. We have two types of datasources that we use persistent and non-persistent. And we are using the Oracle thin driver – non-XA for RAC Service Instances, supporting global transactions.
When we do failover to the 2nd node we get a nasty exception in our GUI but after logging out and logging back it we are fine.
My question is that I assumed I shouldn't have to restart our web-application and it should have stayed up ?? Or is there something wrong with our setup ?
Thanks,
Ian

Showing us the exception and/or the error messages at the server might help...
Note that failing over does not save any ongoing connection or transaction that
had been to the dead RAC node... Does your web-app get-use-close JDBC
connections on a per-user-invoke basis, or does it hold onto connections?
Joe

Fail over not reliable

          When my database fails over, my weblogic 5.1 (sp10) cluster doesn't always reconnect
          when the DB comes back up. It just works for a minute or so, then freezes....
          no errors... I have tested the DB and it is fine, if I restart my app-servers
          they reconnect just fine. As it stands, i get about a 50% success ratio on the
          fail-over.
          I have the following setting for my connection Pool :
          weblogic.jdbc.connectionPool.ejbPool=\
          url=jdbc20:weblogic:oracle,\
          driver=weblogic.jdbc20.oci.Driver,\
          loginDelaySecs=0,\
          initialCapacity=5,\
          maxCapacity=35,\
          capacityIncrement=2,\
          allowShrinking=true,\
          shrinkPeriodMins=5,\
          refreshTestMinutes=1,\
          testConnsOnReserve=true,\
          testConnsOnRelease=true,\
          testTable=dual,\
          props=user=ZZZ;password=YYY;server=XXX;
          ANY help would be appreciated.
          Thanks,
          Jacques


Have you tried resetting the connection pool manually when the database
          server fails over? You can do this via the weblogic.Admin Java program
          from the command line so it is scriptable. Typically, I recommend that
          you add this to your database fail-over scripts so that as soon as the
          database comes back up, the script invokes the command to reset the
          connection pool on each server...
          Raj Alagumalai wrote:
          > Jacques,
          >
          > The value that you have set for refreshTestMinutes is very low.
          >
          > > refreshTestMinutes=1,\
          >
          >
          >
          > This will cause the server to refresh every connection not being used
          > every minute. I would suggest that you increase this value and enable
          > jdbc logging and test failover
          >
          > Thanks
          >
          >
          > Raj Alagumalai
          > Developer Relations Engineer
          > BEA Support
          >
          >
          >
          > jacques Vigeant wrote:
          >
          >> When my database fails over, my weblogic 5.1 (sp10) cluster doesn't
          >> always reconnect
          >> when the DB comes back up. It just works for a minute or so, then
          >> freezes....
          >> no errors... I have tested the DB and it is fine, if I restart my
          >> app-servers
          >> they reconnect just fine. As it stands, i get about a 50% success
          >> ratio on the
          >> fail-over.
          >> I have the following setting for my connection Pool :
          >> weblogic.jdbc.connectionPool.ejbPool=\
          >> url=jdbc20:weblogic:oracle,\
          >> driver=weblogic.jdbc20.oci.Driver,\
          >> loginDelaySecs=0,\
          >> initialCapacity=5,\
          >> maxCapacity=35,\
          >> capacityIncrement=2,\
          >> allowShrinking=true,\
          >> shrinkPeriodMins=5,\
          >> refreshTestMinutes=1,\
          >> testConnsOnReserve=true,\
          >> testConnsOnRelease=true,\
          >> testTable=dual,\
          >> props=user=ZZZ;password=YYY;server=XXX;
          >>
          >>
          >> ANY help would be appreciated.
          >> Thanks,
          >> Jacques
          >>
          >

SQL Server 2014 Always on HA takes 8-14 seconds to fail over. Application side timeouts occur

Hi All,
I have a very similar post in the SQL Server 2014 forums too (https://social.technet.microsoft.com/Forums/sqlserver/en-US/adb5e338-907e-4405-aa62-d3ea93c7a98a/sql-server-2014-always-on-ha-takes-814-seconds-to-fail-over-application-side-timeouts-occur?forum=sqldisasterrecovery) -
advice in the end was to post a question here.
SQL Server Nodes, 2014 (12.0.2480.0)
1 Share witness (on separate subnet)
1 Cluster
1 Listener
I have been testing the response time to failovers – both manual (right-click, fail over in SSMS) and Automatic (shut down the primary host). The way I am testing response is to have a SSMS query running on my desktop, connected to the listener querying
a small table and hit execute.
The Query response time, from execute to receiving the result, has been between 8 and 14 seconds based on my testing. My previous experience (in a separate environment) showed around 2 second fail over times in a very similar configuration.
Availability DB is 200Mb and is not actively used. The nodes are synchronised.
SQL Server Hosts: Windows 2012, 2 cpu, 8gb RAM.
Questions:
1: It’s a big question but what should I expect for a ‘normal’ fail over time. Keep in mind this scenario is about as simple as it gets.
2: As it stands an 8 to 14 second ‘outage’ could cause some applications to time out. Or am I being un-reasonable? I am seeing the very simple query in SSMS to time out with this:
Msg 983, Level 14, State 1, Line 2
Unable to access availability database 'DATABASE' because the database replica is not in the PRIMARY or SECONDARY role. Connections to
an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later.
Cluster logs are long - this section accounts for 8 seconds of the 11 second outage I experienced. I can supply the full log if required. Also this log is just the 2 cluster nodes, I removed the witness share to make sure it was as simple as possible.
00001090.00002128::2015/02/25-03:05:08.255 INFO [GEM] Node 2: Deleting [1:65 , 1:71] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:10.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:11.888 INFO [GEM] Node 2: Deleting [1:72 , 1:73] (both included) as it has been ack'd by every node
00001090.00002698::2015/02/25-03:05:11.889 INFO [GUM] Node 2: Processing RequestLock 2:49
00001090.00002128::2015/02/25-03:05:11.890 INFO [GUM] Node 2: Processing GrantLock to 2 (sent by 1 gumid: 67)
00001090.00002698::2015/02/25-03:05:11.890 INFO [GUM] Node 2: executing request locally, gumId:68, my action: /dm/update, # of updates: 1
00001090.00002128::2015/02/25-03:05:12.890 INFO [GEM] Node 2: Deleting [1:74 , 1:74] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:15.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:16.988 INFO [GUM] Node 2: Processing RequestLock 1:28
Thanks in advance.
Keegan

Hi Keegan,
From these event log , what I can see is "Sending request Netname" wasted the time .
Could you please tell us the network configuration of that cluster nodes ?
If I recall correctly , it is recommended to only remain Tcp/IP protocol and disable NetBIOS over TCP/IP for "Private Network" , also do not configure DNS/Wins default gateway for "Private Network" :
https://support.microsoft.com/kb/258750?wa=wsignin1.0
After that please test again .
Best Regards,
Elton JI
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Front End pool failed over

Hi all,
1. I setup a pool with three Front End servers (FQDN of pool is pool.site1.sip96x2.com and it's pointed to IP address of three Front End servers). Everything works fine. But When I disable network interface on FE1 and FE2, the Lync clients are disconnected.
I haven't understood clearly how the Lync clients failed over in a pool? Please clarify to me.
2. I have two central site (Root site and Primary site, they have different domain sip96x2.com and site1.sip96x2.com). The simple URL dialin is pointed to Front End server at Root site. So if the link between Root site and Primary site is down, how can the
users at Primary site connect to dialin URL?
3. In building topology for Front End pool, I checked Override FQDN internal web service and the FQDN is "poolint.site1.sip96x2.com". I created three A records "poolint.site1.sip96x2.com" and pointed to three IP addresses of Front End
servers. Is it right?
Thanks so much!

Ah ok, well first thing if I am reading this correctly, pool pairing Standard with Enterprise is not supported. You should only pair Standard with Standard and Enterprise with Enterprise (even though topology builder won't stop you) Take a look here for
support scenarios http://technet.microsoft.com/en-us/library/jj204697.aspx
To deal with the simple URLs in the event of failover you need to add them using Powershell. Take a look at this article which explains and gives an example: http://blogs.perficient.com/microsoft/2012/01/configuring-simple-urls-for-multiple-lync-pools/
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
Georg Thomas | Lync MVP
Blog www.lynced.com.au | Twitter
@georgathomas
Lync Edge Port Check (Beta)

How Front End pool deals with fail over to keep user state?

   Hello to all, I searched a lot of articles to understand how Lync 2010 keeps user state if a fail happens in a Front Pool node, but didn't find anything clear.
     I found a MS info. about ths topic : " The Front End Servers maintain transient information—such as logged-on state and control information for an IM, Web, or audio/video (A/V) conference—only for the duration of a user’s session.
This configuration
is an advantage because in the event of a Front End Server failure, the clients connected to that server can quickly reconnect to another Front End Server that belongs to the same Front End pool. "
    As I read, the client uses DNS to reconnect to another Front End in the pool. When it reconnects to an available server, does he lose what he/she was doing at Lync client? Can the server that is now hosting his section recover all
"user's session data"? Is positive, how?
   Regards, EEOC.

The presence information and other dynamic user data is stored in the RTCDYN database on the backend SQL database in a 2010 pool:
http://blog.insidelync.com/2011/04/the-lync-server-databases/ If you fail over to another pool member, this pool member has access to the same data.
Ongoing conversations and the like are cached at the workstation.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

OVI fails to connect to Nokia N8 on "Checking the ...

Hi All,
I'm having problems connecting OVI to a Nokia N8-00 handset via Bluetooth.
The Add New Device wizard is able to detect the phone but when selecting it from the list and proceeding it stays on "Checking the Bluetooth capabilities of your device." for some 20 seconds after which it eventually fails with the error of "Failed to connect to your device. Problems occured while authorising the Bluetooth connection between your device and computer."
I've verified that both devices are configured as authorised by their respective counterpart.
Also tried to remove the pairing from both the laptop and phone and re-pair them again - same problem.
I am able to sync the phone with OVI via USB no problem.
I am also able to use my OVI with another Nokia phone (E72) via Bluetooth without any issues.
This points me to a possible problem with Bluetooth on the N8 phone itself but I don't have any way to prove it.
I wonder if anybody else has experienced the same issue?
OVI version 3.0.0.290
N8-00 version 013.016
Thanks, Jan

All bluetooths stack versions, OVI versions, PC Suite versions are same as those of another laptop which connects well over bluetooth.
By the way still, my Win7 Home Premium's OVI's system info tells that it is using Microsoft Bluetooth Stack Version 6.1.7600 build 16385 (Active & In Use).
PLS DO HELP. OTHERWISE I'VE NO OPTION BUT TO LOOK FOR ANOTHER SYMBIAN 3 DEVICE. I DON'T WANT TO PART WITH MY N8 OR MY ACER ICONIA TABLET.
Note: This problem seems only with N8 because I've tried other nokia models. They all connect well. But I've also tried another N8, that also DIDN'T CONNECT. What the heck problem is with N8.
Wish#1: MP3 Tag Editor capable of editing ratings.
Wish#2: Android type Video player, highly efficient player capable of playing all formats.
Wish#3: Without Google Maps (and products), no gadget is worth keeping.
Attachments:
Ovi system info.png ‏19 KB

JDBC - Fail over connection

Similar Messages

Maybe you are looking for