and closing connections
Correct me if I'm wrong but if the first con.close() call
succeeds your code will still execute the second con.close()
call in the finally block won't it?
Closing the connection won't necessarily dereference the
con variable, so it's trying to close a connection
Yes you have to close the connections! Nothing will drop your server
faster than running out of DB connections.
If you open your connection with this:
Connection conn = DriverManager.getConnection(url, user, password);
Then you close it like this:
conn.close();
--- Hari Yellina [EMAIL
do that.
Sincerely,
Sergei Batiuk.
IT department
Damen Shipyards Okean
+380 512 293146
+380 512 293329
-Original Message-
From: Hari Yellina [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 12, 2002 8:10 AM
To: Tomcat Users List
Subject: Closing Connections.
Hi All,
Is it neccesary
Hi All,
Is it neccesary for us to close the connetions for the database. Is the
java garbage collector gonna do the job for us.
If that is not the case please tell me how to close the connections. We have
a application containing 800 pages . Every page has a connection open . Do
we require to
I now have 3.2.3 installed and get the same behaviour. Any ideas?
Thanks,
George
- Original Message -
From: Rob S. [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, August 14, 2001 12:49 AM
Subject: RE: Is Tomcat not closing connections?
Hi George,
Tomcat 3.2.3 is the latest
Hi,
I have tomcat 3.1.1 installed on a solaris box. It is talking to apache on a
different solaris box.
Apache is setup to have a maximum of 256 processes but rarely actually goes
above 150.
When I check how many connections are talking to port 8007 I get over 400
using the following command :
