Kathi Schleidt
2017-05-02 14:45:14 UTC
Hiya,
Looks like there’s a problem with App Schema and PostGIS connections,
each time I restart GeoServer, I get new connections on my PostGIS DB
while the old ones are retained. Interesting is that when one stops
GeoServer on Tomcat, then restarts PostGIS, most of these hanging
connections are reestablished (although GeoServer has yet to be
restarted). The final effect is that after a few GeoServer restarts (btw
– is it now possible to reload App Schema configs without restarting
GeoServer?) all available DB connections are taken by hanging (idle)
connections; nothing works. (can’t quite remember if just restarting
TomCat was enough to get rid of these dead connections, at the end of
the day we just restarted the machine to get rid of them).
I’ve tried to make sense of the behavior based on the number of hanging
connections (my GeoServer has 10 app schema workspaces as well as 5
simple PG connections configured to the same database), but haven’t
managed to get a clear picture of what’s really hanging. However, each
time I restart GeoServer, at least 13 new connections are added (that
don’t go away), a few more come when the application requests data, but
these seem to go away again). A few restarts later everything is locked
down again.
Has anybody observed a similar behavior? Have a solution?
:?
Kathi
DB: PostgreSQL 9.3.16 on x86_64-unknown-linux-gnu, compiled by gcc
(Debian 4.7.2-5) 4.7.2, 64-bit
GeoServer: 2.10.2
Debian GNU/Linux 7 (wheezy)
--
_________________________________________________________________________
Katharina Schleidt
Tel: +43 (1) 89 234 26
Mobile: +43 (650) 89 234 26
Skype: Kathi Schleidt
***@Schleidt.org
www.schleidt.org/kathi
The world is a dangerous place to live; not because of the people who are evil, but because of the people who don't do anything about it - Albert Einstein
Growth for the sake of growth is the ideology of the cancer cell – Edward Abbey
If at first, the idea is not absurd, then there is no hope for it - Albert Einstein
Looks like there’s a problem with App Schema and PostGIS connections,
each time I restart GeoServer, I get new connections on my PostGIS DB
while the old ones are retained. Interesting is that when one stops
GeoServer on Tomcat, then restarts PostGIS, most of these hanging
connections are reestablished (although GeoServer has yet to be
restarted). The final effect is that after a few GeoServer restarts (btw
– is it now possible to reload App Schema configs without restarting
GeoServer?) all available DB connections are taken by hanging (idle)
connections; nothing works. (can’t quite remember if just restarting
TomCat was enough to get rid of these dead connections, at the end of
the day we just restarted the machine to get rid of them).
I’ve tried to make sense of the behavior based on the number of hanging
connections (my GeoServer has 10 app schema workspaces as well as 5
simple PG connections configured to the same database), but haven’t
managed to get a clear picture of what’s really hanging. However, each
time I restart GeoServer, at least 13 new connections are added (that
don’t go away), a few more come when the application requests data, but
these seem to go away again). A few restarts later everything is locked
down again.
Has anybody observed a similar behavior? Have a solution?
:?
Kathi
DB: PostgreSQL 9.3.16 on x86_64-unknown-linux-gnu, compiled by gcc
(Debian 4.7.2-5) 4.7.2, 64-bit
GeoServer: 2.10.2
Debian GNU/Linux 7 (wheezy)
--
_________________________________________________________________________
Katharina Schleidt
Tel: +43 (1) 89 234 26
Mobile: +43 (650) 89 234 26
Skype: Kathi Schleidt
***@Schleidt.org
www.schleidt.org/kathi
The world is a dangerous place to live; not because of the people who are evil, but because of the people who don't do anything about it - Albert Einstein
Growth for the sake of growth is the ideology of the cancer cell – Edward Abbey
If at first, the idea is not absurd, then there is no hope for it - Albert Einstein