Hi list,
i’m doing some stress tests on geoserver with the apache jmeter tool. I’m simulating 5 concurrent users (by 5 threads) each with 10 sequential requests in an interval of 1 second (alltogether 50 requests in 10 seconds). That shouldn’t be too much for geoserver because it’s running on a double quad core machine with 16GB RAM and WIN 2003 platform. As Backend i am using ArcSDE on Oracle (i’m using geoserver 1.6.3, tomcat 5.5.26)
I was just getting a handful of images back from geoserver with every test while the vast majority didn’t work . When looking at the log, i found this error:
“java.util.NoSuchElementException: Could not aquire feature:org.geotools.data.DataSourceException: The maximun of 2 to org.geotools.arcsde.pool.ArcSDEConnectionConfig[dbtype=arcsde, server=srvumwgeo005.umwelt.hessen.de, port=5151, instance=null, user=geoview_user, password=*****, minConnections=2, maxConnections=2, connTimeOut=1000] has been reached”
Hence i was changing the datastore configuration. Setting up the pool.maxConnections up to 8 and the pool timeout up to 8000ms. That showed no success. Still the same error. Even the “maxConnections=2, connTimeOut=1000” was still the same and didn’t change (Although the configuration window shows the right values). I restartet tomcat. Still the same error. I restarted the whole server (sometimes its necessary on windows machines). Still the same. It looks like my settings of maxConnections wasn’t beeing taken from geoserver.
I also stopped some other services to release connections to ArcSDE and increased the maximum numbers of connections of ArcSDE. But still the same with geoserver WMS. It looks like the problem is geoserver-side.
I attached a verbose log of the last test to the mail. Hope that someone knows where the problem could be.
Thanks
Albrecht
–
Albrecht Weiser,
E6, GIS Center
Hessische Zentrale für Datenverarbeitung (HZD)
Mainzer Straße 29, 65185 Wiesbaden
E-Mail: albrecht.weiser-at-hzd.hessen.de
Hi albercht,
I notice you're using geoserver 1.6.3. Hence, I suggest you to try out with a
newer version (1.7.0 should work) since the arcsde plugin was improved a big
deal since 1.6.3, and one of the aspects it got better is on connection
handling.
I'm not sure why exactly you're getting that behaviour in 1.6.3, but truth is,
that's dead code no longer maintained so if you can switch to a newer version
that'd be great.
Waiting for your comments.
Cheers,
Gabriel
On Thursday 06 November 2008 02:04:18 pm Albrecht.Weiser@anonymised.com wrote:
Hi list,
i'm doing some stress tests on geoserver with the apache jmeter tool. I'm
simulating 5 concurrent users (by 5 threads) each with 10 sequential
requests in an interval of 1 second (alltogether 50 requests in 10
seconds). That shouldn't be too much for geoserver because it's running on
a double quad core machine with 16GB RAM and WIN 2003 platform. As Backend
i am using ArcSDE on Oracle (i'm using geoserver 1.6.3, tomcat 5.5.26) I
was just getting a handful of images back from geoserver with every test
while the vast majority didn't work . When looking at the log, i found this
error: "java.util.NoSuchElementException: Could not aquire
feature:org.geotools.data.DataSourceException: The maximun of 2 to
org.geotools.arcsde.pool.ArcSDEConnectionConfig[dbtype=arcsde,
server=srvumwgeo005.umwelt.hessen.de, port=5151, instance=null,
user=geoview_user, password=*****, minConnections=2, maxConnections=2,
connTimeOut=1000] has been reached" Hence i was changing the datastore
configuration. Setting up the pool.maxConnections up to 8 and the pool
timeout up to 8000ms. That showed no success. Still the same error. Even
the "maxConnections=2, connTimeOut=1000" was still the same and didn't
change (Although the configuration window shows the right values). I
restartet tomcat. Still the same error. I restarted the whole server
(sometimes its necessary on windows machines). Still the same. It looks
like my settings of maxConnections wasn't beeing taken from geoserver. I
also stopped some other services to release connections to ArcSDE and
increased the maximum numbers of connections of ArcSDE. But still the same
with geoserver WMS. It looks like the problem is geoserver-side. I attached
a verbose log of the last test to the mail. Hope that someone knows where
the problem could be. Thanks
Albrecht
--
Albrecht Weiser,
E6, GIS Center
Hessische Zentrale für Datenverarbeitung (HZD)
Mainzer Straße 29, 65185 Wiesbaden
E-Mail: albrecht.weiser-at-hzd.hessen.de