Re: How to kill a connection

From: gnazio (usenet.user_at_email.it)
Date: 12/10/03 

Date: 9 Dec 2003 16:54:23 -0800

bobrivers@pobox.com (Bob Rivers) wrote in message news:<aa669e9b.0312090937.56e10045@posting.google.com>...
> Hi,
>
> I have a problem, and I don't know how to solve it.
>
> We have a web application (done in java/jsp, running under tomcat
> 4.1.29/j2sdk 1.4.2) that establishes a connection with postgres 7.3.2.
>
> We are using jdbc (7.3.1) to do it, but we are not using connection
> pool (my client security police determine that all connections to the
> database must be done per user basis).
>
> So, when the user do the login, we create a connection to this user.
> When the user closes the application, we close the connection. No
> problem, everything works well.
>
> But, if the user closes the window abnormally (for example, shutting
> down the browser window without clicking my application logoff button)
> the connection opened will be open forever.
>
> This connection will be killed only if I shutdown tomcat and/or
> postgres.
>
> My question is: How do I kill an idle connection?
>
> I don't want to do it manually. I was thinking about a thread that
> verifies the connection. If this connection is idle more that x
> minutes, I could kill it.
>
> Another way, is to setup a timeout for the connection. If it is idle
> for more that x minutes, postgres should kill it automatically.
>
> Is it possible? How do I do that?
>
> TIA,
>
> Bob

I worked on a project with tomcat ~4.18 and oracle (developed on
websphere but switched to tomcat because it was too expensive for our
customer).
There was a legacy client-server application accessing the same
database and so I should leave it unmodified.
The security for that application was designed using the rdmbs
authentication/authorization.
Moreover every operation was logged on a table by triggers and the
username was also logged.
I've found that with that version of tomcat, the method
getConnection(String username, String password) on the tomcat
datasource was not implemented and so the triggers wasn't able to know
who was making what.
Now I've heard that the method has been implemented and so every
connection from the pool should result 'opened' by the username passed
to the method.
Differently I solved my problem using tyrex (now at
http://tyrex.sourceforge.net/) and I think that it's an even better
option.
Your code could gain in efficiency and, why not, also in elegance.
I hope I can help you if you need help with it.

p.s.
please, feel free to correct my English...I'd like to improve myself
with it! :-)