JDBC Program not going away after closing database records

I have Java Servlets and JSP working great with Oracle 9i database using JDBC Thin Driver in our Apache Tomcat Container sitting on Windows 2000 server.

Everytime I go into an Oracle record with my Java front end web page I notice that I am opening a program calledJDBC Thin Client.

Basically I am testing it out by opening records in the Front end JSP and then checking in SQL Plus to see what is going on in the database.

I use this command in my SQL Plus tool:

select username, program, status, server from v$session where username = 'jones';

The issue is theJDBC Thin Client Program seems to not disappear even though I am closing my database connections in aJava Finally block.

The below shows the output from the SQL Plus if I open 3 different records (open record, then close the record and then open up another record) in my Java web page.

SQL Plus results using:select username, program, status, server from v$session where username = 'jones';

UsernameProgram StatusServer

jonesJDBC Thin ClientInactiveDedicated

jonessqlplus.exe ActiveDedicated

jonesJDBC Thin ClientInactiveDedicated

jonesJDBC Thin ClientInactiveDedicated

It showsJDBC Thin Client program running 3 times.

Is theJDBC Thin Client program draining resources from our Oracle 9i database even if the status saysinactive? TheJDBC Thin Client Programs seem to not go away.

Please advise.

[1532 byte] By [oaklandara] at [2007-11-27 5:57:52]
# 1
http://en.wikipedia.org/wiki/Connection_Pool
dcmintera at 2007-7-12 16:31:31 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...
# 2

In addition to open connections, v$session contains connections that have been recently closed. Nothing to be alarmed about; it's normal Oracle behaviour.

See here: http://oracleandy.blogspot.com/2006_03_01_archive.html

or google for something like "v$session" closed connections.

sjasjaa at 2007-7-12 16:31:31 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...
# 3

Thanks for the info.

It turns out I had two areas I was not closing my Database connections.

I closed them and now everything is okay with no JDBC Thin Client programs showing up.

Do I need a Connection Pool for a Database that is only hit on at most 10 times a day and hardly ever has Concurrent users hitting on it?

oaklandara at 2007-7-12 16:31:31 > top of Java-index,Database Connectivity,Java Database Connectivity (JDBC)...