Program draining database resources?

[dreampolice]

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 I notice that I am opening a program called JDBC Thin Client.

Basically I am testing it out by opening records on the Front end web page and then checking in SQL Plus what is going on in the database.
I use this command:
select username, program, status, server from v$session where username = 'jones';

The issue is the JDBC Thin Client Program seems to not disappear even though I am closing my database connections in a Java Finally block.

Here is how the output looks in 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:

Username   Program             Status        Server
jones      JDBC Thin Client    Inactive      Dedicated
jones      sqlplus.exe         Active        Dedicated
jones      JDBC Thin Client    Inactive      Dedicated
jones      JDBC Thin Client    Inactive      Dedicated

It shows JDBC Thin Client program running 3 times.
Is the JDBC Thin Client program draining resources from our Oracle 9i database even if the status says inactive? The JDBC Thin Client Programs seem to not go away.

Please advise.

 

[Turkbear]

Hi,
It is not running - Inactive connections will be cleaned out eventually (by PMON, I think) - I do not believe they are any real drain on resources..








To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[dreampolice]

Thanks,

That info is good to know.

I had two areas where I was not closing my connections in my Java Class files. After I closed them it eliminated the problem.

 

[Turkbear]

Hi,
OOPs, PMON handles 'failed' sessions not the inactive ones..They will eventually go away but I forget where the time period is controlled..Explicitly closing is always a good idea..





To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[dreampolice]

Thanks for the second time on more additional info.

I found that if I didnt explicitly close my connections the only way it (JDBC Thin Client) would close was by shutting down and restarting the Tomcat Container which I did once a day in my development environment.