From: | Hunter Hillegas <lists(at)lastonepicked(dot)com> |
---|---|
To: | Ben Carterette <bcarterette(at)mail(dot)liberty(dot)k12(dot)mo(dot)us>, PostgreSQL <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: my connections never die |
Date: | 2001-05-10 17:08:40 |
Message-ID: | B7201928.16149%lists@lastonepicked.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Are you using servlets?
I would have to say that not explicitly closing connections is bad... If you
are using servlets, you can register an event for when the session expires
to close the connection. That way you know it's not hanging on to stuff
forever.
Hunter
> From: Ben Carterette <bcarterette(at)mail(dot)liberty(dot)k12(dot)mo(dot)us>
> Organization: Liberty Public School District
> Date: Thu, 10 May 2001 11:11:05 -0500
> To: pgsql-general(at)postgresql(dot)org
> Subject: [GENERAL] my connections never die
>
> I'm running a web server on one machine (Apache 1.3+Tomcat 3.2+mod_jk)
> with some databases (postgresql 7.1), and a dedicated database server on
> another machine (postgresql 7.0.2). A lot of my web pages establish a
> connection to a database on either machine and store the Connection
> object in a session so's I don't have to create a new one every page.
> Well, it seems these connections, which never get explicitly closed, are
> never dying. Some of them, anyway. I haven't been able to predict
> which ones are going to close themselves and which ones will stay open
> for days, but some of them are still taking up a process days later.
>
> Greatly appreciating any explanation,
> Ben Carterette
> bcarterette(at)mail(dot)liberty(dot)k12(dot)mo(dot)us
From | Date | Subject | |
---|---|---|---|
Next Message | newsreader | 2001-05-10 18:08:56 | very odd behavior |
Previous Message | John Coers | 2001-05-10 16:57:19 | Re: COPY locking |