I am connecting to Oracle 9i using JDBC in my JSP/Servlets web pages with Tomcat 6.0.20 container. I am closing all my connections in Finally blocks. Everything works great during the day with JDBC and Oracle where only 2 people are using the web site with about 300 small records in the Oracle database.
But after a Web crawler runs through our web server at 3 AM the next morning a v$session check shows several lines of JDBC Thin Client inactive status marked at 3 AM. Any way to find exactly what sql statement or program that could be causing the JDBC Thin Client to show up?
What are you doing? You are supposed to be reading this tiny ad!
the new thread boost feature brings a LOT of attention to your favorite threads