Win a copy of Cloud Native PatternsE this week in the Cloud forum
or Natural Language Processing in the AI/ML forum!
    Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Devaka Cooray
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
  • Paul Clapham
  • Knute Snortum
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Piet Souris
  • Stephan van Hulst
  • Carey Brown
  • Tim Holloway
  • Frits Walraven
  • Ganesh Patekar

JDBC connection in Oracle db

Posts: 13
  • Mark post as helpful
  • send pies
  • Report post to moderator

I have a simple application; I am not using connection pool & creating connection object on every request & closing the connection after completion of request.
Ideally, number of connection at a time should be number of request at a time to the application; but it's not working like that;
even if there are 5 users; it shows 60 connections sometimes (status - INACTIVE) from JDBC in Oracle database.

I am thinking to make
connection_object = null;
after closing it (connection_object.close(); ).

But not sure whether it would be helpful or not because close() method releases the db connection immediately.
Is it possible to destroy the connection immediately by connection_object = null; or some other way?

Please let me know if you have any suggestions.

Thanks & Regards...
[ October 27, 2006: Message edited by: Mira Mehta ]
Posts: 1364
  • Mark post as helpful
  • send pies
  • Report post to moderator
Please don't crosspost.

Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic
Boost this thread!