yes, the fix should have been included in the 1.7.0 release. A few questions:
1. What are the connection pool settings when you set up the postgis data store?
2. Are you running via the war in a servlet container? or standalone? If the former which servlet container?
3. What sort of requests are being executed. Is this when viewing KML in Google Earth?
Thanks,
-Justin
laurent pierrre wrote:
Hi Justin,
I've just installed 1.7.0 this morning and I've got the same problem with too many connections to Postgres. I tried to increase the max number from 30 to 40 but if I do that I get another problem from Postgres dealing with kernel size .... so it is not an option for me. Is your bug fix included in the downloadable 1.7 version ?
Cheers
Laurent
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
We have faced the same phenomena with Oracle datastore. Our Geoserver version is 1.7.0 and we have been using both the Oracle driver shipped with the 1.7.0. release and a development version (Oracle NG). We are having now a standard installation with Jetty, and we are serving just WFS 1.0.0.
-Jukka Rahkonen-
-----Alkuperäinen viesti-----
Lähettäjä: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Lähetetty: pe 7.11.2008 18:53
Vastaanottaja: laurent pierrre
Kopio: geoserver-users
Aihe: Re: [Geoserver-users] many connections
Hi Laurent,
(moving this the public mailing list)
yes, the fix should have been included in the 1.7.0 release. A few
questions:
1. What are the connection pool settings when you set up the postgis
data store?
2. Are you running via the war in a servlet container? or standalone? If
the former which servlet container?
3. What sort of requests are being executed. Is this when viewing KML in
Google Earth?
Thanks,
-Justin
laurent pierrre wrote:
Hi Justin,
I've just installed 1.7.0 this morning and I've got the same problem
with too many connections to Postgres. I tried to increase the max
number from 30 to 40 but if I do that I get another problem from
Postgres dealing with kernel size .... so it is not an option for me.
Is your bug fix included in the downloadable 1.7 version ?
Cheers
Laurent
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Can I ask you to please use the public mailing for replies. Reply-All vs just Reply. Thanks :).
1. What are the connection pool settings when you set up the postgis data store?
You mean max nuber of connections for Postgres, I managed to extent it from 30 to 100.
I actually meant the configuration for the connection pool when configuring the GeoServer feature type. Same place the host, port, datbase, etc... is specified. The default is min connections = 4 and max connections = 10. Did you change these parameters at all?
Also... are you running out of connections even with 100 connections for postgres? or just with 30?
Can you include the output of the command `ps -u postgres` at the time you run out of connections. Thanks.
2. Are you running via the war in a servlet container? or standalone? If the former which servlet container?
Glassfish
3. What sort of requests are being executed. Is this when viewing KML in Google Earth?
Yes KML for OpenLayers
Cheers
Laurent
laurent pierrre wrote:
Hi Justin,
I've just installed 1.7.0 this morning and I've got the same problem with too many connections to Postgres. I tried to increase the max number from 30 to 40 but if I do that I get another problem from Postgres dealing with kernel size .... so it is not an option for me. Is your bug fix included in the downloadable 1.7 version ?
Cheers
Laurent
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
It may or may not be useful in this specific case, but users of the PostGIS datastore may wish to know that what Mr. Pierre is calling "another problem from Postgres dealing with kernel size" is, if I recognize it correctly, a controllable issue if you have access to the kernel parameters:
I found it helpful in scaling (we're running a large GeoServer instance and a GeoNetwork instance out of the same PostgreSQL instance) to bump up SHMMAX and allow PostgreSQL to eat hearty.
---
A. Soroka / Digital Scholarship Services R & D
the University of Virginia Library
On Nov 10, 2008, at 12:51 PM, Justin Deoliveira wrote:
laurent pierrre wrote:
Hi Justin,
I've just installed 1.7.0 this morning and I've got the same problem
with too many connections to Postgres. I tried to increase the max
number from 30 to 40 but if I do that I get another problem from
Postgres dealing with kernel size .... so it is not an option for
me. Is your bug fix included in the downloadable 1.7 version ?
Cheers
Laurent
Hi Justin
Le 10 nov. 08 à 18:51, Justin Deoliveira a écrit :
Hi Laurent,
Can I ask you to please use the public mailing for replies. Reply-All vs just Reply. Thanks :).
1. What are the connection pool settings when you set up the postgis data store?
You mean max nuber of connections for Postgres, I managed to extent it from 30 to 100.
I actually meant the configuration for the connection pool when configuring the GeoServer feature type. Same place the host, port, datbase, etc... is specified. The default is min connections = 4 and max connections = 10. Did you change these parameters at all?
No I didn't
Also... are you running out of connections even with 100 connections for postgres? or just with 30?
Only with 30. Now I managed to extend my shared memory in order to get 100 connections
And I have another question about datastores : as long as you don't use one, does it use the connection pool ?
We have faced the same phenomena with Oracle datastore. Our Geoserver
version is 1.7.0 and we have been using both the Oracle driver
shipped with the 1.7.0. release and a development version (Oracle
NG). We are having now a standard installation with Jetty, and we are
serving just WFS 1.0.0.
Jukka, Laurent, this morning I spent some time trying to replicate
the connection exhaustion, but so far failed.
I did the following:
- configured my postgis to allow max 20 connections
- configured not one but two postgis datastores in my configuration,
each using the same database (just to increase the load a bit)
- started playing with configuration options, adding features types,
configuring them, removing them... nothing
- not happy, I started a long WMS threaded benchmark using 80 concurrent
threads to hit the connection pools (limited to 10 connections)
and played configuration while it was running. Again nothing (actually
something, but not pool exhaustion, will talk about this later)
- tried again with a WFS benchmarks instead, same result, did not manage
to get any error pool size wise
Soo... can you tell me what you are doing to get out of connections?
Cheers
Andrea
PS: the extra thing I noticed is that when you hit "apply" all requests
that are executing against a connection pool fail immediatly because
the datastore is recreated (to account for possible changes in its
configuration) and the pool disposed, so the old connections
disappear. To avoid this we'd have to use JNDI based connection
pools.
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
