A bug in ORACLE JDBC close Connection?
From: Sun (sun_2003_at_email.it)
Date: 01/30/04
- Next message: Stu Charlton: "Re: choices regarding where to place code - in the database or middletier"
- Previous message: Vladimir Andreev: "Re: choices regarding where to place code - in the database or middletier"
- Next in thread: Ronald Cole: "Re: A bug in ORACLE JDBC close Connection?"
- Reply: Ronald Cole: "Re: A bug in ORACLE JDBC close Connection?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 30 Jan 2004 16:40:59 GMT
Hi to all friends!
I have a big problem. My application is running on Tomcat 4.0.5 and
uses an ORACLE db:
Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
Connection conn=DriverManager.getConnection
("jdbc:oracle:thin:@xxx.xxx.xxx.xxx:xxxx:xxx","******","*****");
I am sure that every connection that I open is also closed
but last night, after a great work,
ORACLE didn't accept any connection because the maximum number
of connection was reached.
My application is the only that at the moment uses ORACLE.
Is it possible that there is a bug in the JDBC driver,
included in ORACLE installation, that does not really close
connections to the db?
I use the Oracle8i Enterprise Edition Release 8.1.7.4.0
Many thanks to all
Riccardo
- Next message: Stu Charlton: "Re: choices regarding where to place code - in the database or middletier"
- Previous message: Vladimir Andreev: "Re: choices regarding where to place code - in the database or middletier"
- Next in thread: Ronald Cole: "Re: A bug in ORACLE JDBC close Connection?"
- Reply: Ronald Cole: "Re: A bug in ORACLE JDBC close Connection?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
