Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Exception-handling
- From: Dave Cramer <pg(at)fastcrypt(dot)com>
- To: Roland Walter <roland(dot)walter(dot)rwa(at)gmx(dot)net>
- Cc: Håkan Jacobsson <hakan(dot)jacobsson99(at)bredband(dot)net>, pgsql-jdbc(at)postgresql(dot)org
- Subject: Re: Exception-handling
- Date: Thu, 21 Dec 2006 12:06:57 -0500
On 21-Dec-06, at 12:04 PM, Roland Walter wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dave Cramer wrote:The only general rule I adhere to is to make sure you clean up your connections in a finally clause DaveDepends of your application. I usually free up all resources in the finally clause, that I do not need any more. The resources are ResultSets and Statements and may be connections. Not closing the Statments and using the same connection further prooved to be fatal.
My point was to make sure you do your cleanup, whatever it may be in a finally clause. This is the most frequent cause of leaking resources.
Dave
Regards, Roland. - -- Dipl.-Phys. Roland Walter mailto: roland (dot) walter (dot) rwa (at) gmx (dot) net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFFir6oxoOEAkary1ERAh1gAJ0XCLT7ildof8QbH/x6y+xrPy4xvACeLBwk vv9oqUJtZGFW/pYCtfLKDUk= =NoBO -----END PGP SIGNATURE-----
- References:
- Exception-handling
- From: Håkan Jacobsson
- Re: Exception-handling
- From: Dave Cramer
- Re: Exception-handling
- From: Roland Walter
- Exception-handling
- Prev by Date: Re: Exception-handling
- Next by Date: use connection pooling
- Previous by thread: Re: Exception-handling
- Next by thread: use connection pooling
- Indexes: