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