jQuery in Action, 3rd edition
The moose likes JDBC and Relational Databases and the fly likes JDBC thin client Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Databases » JDBC and Relational Databases
Bookmark "JDBC thin client" Watch "JDBC thin client" New topic
Author

JDBC thin client

Dan Parsons
Ranch Hand

Joined: May 30, 2007
Posts: 70
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?
 
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
 
subject: JDBC thin client
 
It's not a secret anymore!