Inactive JDBC Thin client sessions
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5

Thread: Inactive JDBC Thin client sessions

Hybrid View

  1. #1
    Join Date
    Dec 2001
    Location
    Keene, NH
    Posts
    510

    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.

  2. #2
    Join Date
    Dec 2001
    Location
    USA
    Posts
    620
    Hi Gopi,

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

    Thanks,
    Sam
    ------------------------
    To handle yourself, use your head. To handle others, use your heart

  3. #3
    Join Date
    Aug 2001
    Posts
    267
    Are you guys tried to use idle time set for profiles or it didn't work in your case.
    Raghu

  4. #4
    Join Date
    Aug 2002
    Location
    Bangalore, India
    Posts
    405
    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.
    -nagarjuna

  5. #5
    Join Date
    Sep 2000
    Location
    Chennai, India
    Posts
    865

    Re: Inactive JDBC Thin client sessions

    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.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width