Thanks Dave, We are using JDBC thin driver. I think there is work around in tomcat called "ValidationQuery" to make sure connection is not dead (which might cause the idle stage of tomcat as per various discussion forums) which needs to configure in context.xml( in tomcat/conf folder).
But I want to confirm whether TAF is compatible with Thin driver or not. I remember our DB talked to oracle support and they supported the OCI driver. but due to other performance issues, we are not looking at OCI driver. Thanks for your response. Shakeel. David Fisher wrote: > > I've been investigating Oracle configuration myself - this page was > helpful to me for Oracle 10g - > http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/htdocs/readme_10201.html > > It contains a reference to the following bug - > >> BUG-3209390 >> JDBC OCI Driver's TAF functionality will not work, when used >> in conjunction with JDBC Fast Connection Failover. The problem is >> that when TAF is enabled, JDBC Fast Connection Failover >> will likely remove connections, that were actually detected >> and failed over by TAF. There is no work-around. Users cannot >> use TAF and Fast Connection Failover together. > > This is also stated for 11g: > http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/htdocs/111070_readme.html > > So I guess you'll need to figure out how - if possible - to > reestablish your connections after the Oracle failover. > > Or, maybe you should use the thin client instead of the OCI? I don't > know the details you should be talking to an Oracle expert on metalink. > > Regards, > Dave > > > On Apr 20, 2009, at 2:30 PM, shak.shaik wrote: > >> >> We've production environment as follows. >> We have two web servers with load balancing capability. We've two >> Oracle DB >> servers and we are using Virtual IP to connect to one of the db >> servers. our >> web server is tomcat 6.0 >> >> <br> >> >> Our application should up and running even there is no DB >> connectivity and >> it is tested and proved. >> Also we use TAF (Transparent Application Failover. if one db server >> is down, >> all db connections has to rout to another db server) as part of its >> db URL. >> <br> >> But last week, one of our DB server got crashed and from the moment >> db got >> crashed, our website is not reachable. >> >> <br> >> When I checked the logs, I didn't see any JDBC exceptions or any other >> generic exceptions. . Same time I saw the status as "started" for >> tomcat >> service in windows service (Control Panel -> Services). >> <br> >> Our network people argue that there are no issues from their side. >> Why the >> tomcat is Idle and web site is not found in case of DB crash? >> <br> >> Any suggestions or work around will be greatly appreciated. >> >> Thanks. >> >> -- >> View this message in context: >> http://www.nabble.com/Tomcat-is-idle-when-Oracle-crashed-tp23145324p23145324.html >> Sent from the Tomcat - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > > -- View this message in context: http://www.nabble.com/Tomcat-is-idle-when-Oracle-crashed-tp23145324p23147710.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
