[Geoserver-devel] GEOS-3727 Not included in 2.0.1?

GeoServer GeoServer Developer
1

Hi all -

I just wanted to clarify this email I received. It looks like this ticket (GEOS-3727) was moved from 2.0.1 to 2.0.2. Does this mean that the issue is not resolved in 2.0.1? Was there some kind of testing done on the fix that did not pass? Any clarification would be appreciated.

THanks,
Sarah

---------- Forwarded message ----------
From: Mark Leslie (JIRA) <jira@anonymised.com…>
Date: Tue, Jan 19, 2010 at 6:54 PM
Subject: [jira] Updated: (GEOS-3727) Unbounded prepared statement pooling can bring Oracle to its knees
To: sarah@anonymised.com

[ http://jira.codehaus.org/browse/GEOS-3727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Leslie updated GEOS-3727:

Fix Version/s: (was: 2.0.1)
2.0.2

Unbounded prepared statement pooling can bring Oracle to its knees

Key: GEOS-3727
URL: http://jira.codehaus.org/browse/GEOS-3727
Project: GeoServer
Issue Type: Bug
Reporter: Andrea Aime
Assignee: Andrea Aime
Fix For: 2.0.2

For most databases prepared statement caching is sort of cheap. For Oracle, it’s not, each prepared statement keeps a cursor open on the server side.
Cursors are usually limited by admins being expensive resources to keep around.
Expose a property to limit the number of cached prepared statements.
Limitless does not sound very good in general, we may want to provide this property for any database that uses prepared statements.

–
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa

For more information on JIRA, see: http://www.atlassian.com/software/jira

2

Sarah Haskins ha scritto:

Hi all -

I just wanted to clarify this email I received. It looks like this ticket (GEOS-3727) was moved from 2.0.1 to 2.0.2. Does this mean
that the issue is not resolved in 2.0.1? Was there some kind of
testing done on the fix that did not pass? Any clarification would
be appreciated.

From what I can see it's just an oversight, I forgot to close the
GeoServer issue when closing the associated GeoTools one.
In any case, it's easy to check: download GS 2.0.1, if the
datastore configuration panel has a way to tune the max amount
of prepared statements then the fix is in, otherwise it's not

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.