Inactive JDBC Thin client sessions

Hello, we have many inactive sessions in our database whose program in v$session is "JDBC Thin Client". Sometimes, the count of these sessions gets dangerously close to the PROCESSES value and I have to manually kill these inactive sessions.

Has anyone experienced this before?

Thanks in advance.

Hi Gopi,

I am having the same problem. Did you get any fix?

Thanks,

Are you guys tried to use idle time set for profiles or it didn't work in your case.

Inactive sessions does not mean bad thing for database as long as they relase the locks immediately after their transaction.

Setting profiles is a good idea.

Quote:

---

Originally posted by gopi
Hello, we have many inactive sessions in our database whose program in v$session is "JDBC Thin Client". Sometimes, the count of these sessions gets dangerously close to the PROCESSES value and I have to manually kill these inactive sessions.

Has anyone experienced this before?

Thanks in advance.

---

Faced this in some of our java applications not all.

This I attribute to programming (bug). The code/process for caching connections and releasing them must be looked into and fine tuned by the programmer.

On the other hand, if the box hosting the application server is restarted then the issue is solved.

So, it is more at the programming level that this has to be handled. (If the job is done disconnect and give up the connection used!)

HTH.