I don't think. Did you try shutting down one node? You can also look
at netadmin tutorial to see what FAILOVER means.
On Fri, Sep 4, 2009 at 11:58 AM, Bill Davidsonbill...@gmail.com wrote:
Mohit Anchlia wrote:
Something like this:
Mohit Anchlia wrote:
Something like this:
(DESCRIPTION=(FAILOVER=ON)(ADDRESS_LIST=(LOAD_BALANCE=ON)(ADDRESS=(PROTOCOL=TCP)(HOST=x)(PORT=1526))(ADDRESS=(PROTOCOL=TCP)(HOST=)(PORT=1526)))(CONNECT_DATA=(SERVICE_NAME=somesid)))
I still haven't been able to locate the documentation,
This is interesting topic.
IANA-failover-expert, but one question comes to my mind. What happens
when the first server is recovered? Some cached connections will still
point to second server, while newly created connections will go to the
first one?
Is that acceptable?
Regards,
Ognjen
-Original Message-
From: Bill Davidson [mailto:bill...@gmail.com]
Sent: Tuesday, September 01, 2009 20:18
To: 'Tomcat Users List'
Subject: Using multiple DataSource's for fail-over.
Tomcat 6.0.20 using DBCP DataSource
Java 1.6.0_16
Oracle 10g with RAC.
I've got two Oracle
I thought the Oracle JDBC driver allowed for all the nodes to be placed
into the connect string and the driver was smart enough to detect
failover. [So its a configuration exercise on the connection string.]
-Tim
Ognjen Blagojevic wrote:
This is interesting topic.
IANA-failover-expert, but
Bill,
If you are using Oracle RAC, then why dont you use a RAC JDBC URL that
contains both nodes?
A DBCP testOnBorrow will ensure only current transactions on a node
will fail if one of the nodes goes down, and all new requests for
connections from the pool will recover.
Bap.
Quoting
Ognjen Blagojevic wrote:
IANA-failover-expert, but one question comes to my mind. What happens
when the first server is recovered? Some cached connections will still
point to second server, while newly created connections will go to the
first one?
Actually, it doesn't switch which is the
Tim Funk wrote:
I thought the Oracle JDBC driver allowed for all the nodes to be placed
into the connect string and the driver was smart enough to detect
failover.
[So its a configuration exercise on the connection string.]
I'm having trouble finding documentation for this capability. Can you
Did you look at Oracle RAC docs?
On Wed, Sep 2, 2009 at 11:10 AM, Bill Davidsonbill...@gmail.com wrote:
Tim Funk wrote:
I thought the Oracle JDBC driver allowed for all the nodes to be placed
into the connect string and the driver was smart enough to detect failover.
[So its a configuration
Something like this:
(DESCRIPTION=(FAILOVER=ON)(ADDRESS_LIST=(LOAD_BALANCE=ON)(ADDRESS=(PROTOCOL=TCP)(HOST=x)(PORT=1526))(ADDRESS=(PROTOCOL=TCP)(HOST=)(PORT=1526)))(CONNECT_DATA=(SERVICE_NAME=somesid)))
On Wed, Sep 2, 2009 at 11:53 AM, Mohit Anchliamohitanch...@gmail.com wrote:
Did
Tomcat 6.0.20 using DBCP DataSource
Java 1.6.0_16
Oracle 10g with RAC.
I've got two Oracle RAC nodes, mirroring each other. My current fail-over
method if the primary node fails is to shut down the web servers,
reconfigure
them to use the secondary node and restart the web servers. Not
11 matches
Mail list logo