Rett,
I do see what you've described, and I do think it's a bug. I believe it was fixed in a recent version of 1.6.x (perhaps SVN only?) which simply avoided the "dispose() on load" issue that you're facing. Can you try the latest release of geoserver (1.6.5?) or a geoserver nightly?
--saul
Rett Hean wrote:
Saul,
Attached is geoserver.log with verbose logging on, if you wish to reference it.
If you search for timestamp 2008-08-06 15:05 that is where I first click on New FeatureType. An error soon follows
2008-08-06 15:05:15,494 DEBUG [data.property] - can't process parameters
I'm not sure if that is related to the error I have been experiencing, but you did mention I look for any errors that may occur before my connection pool error.
Later in the log you will see
2008-08-06 15:05:15,530 DEBUG [arcsde.pool] - populating ArcSDE connection pool
2008-08-06 15:05:16,348 DEBUG [arcsde.pool] - Connection validated, returned user SDE1 second later, the connection pool is closed, because of a dispose call.
2008-08-06 15:05:17,444 INFO [arcsde.data] - DISPOSE: closing connection pool..
2008-08-06 15:05:17,492 DEBUG [arcsde.pool] - SDE connection pool closed. 2008-08-06 15:05:17,492 INFO [arcsde.data] - ArcSDEDataStore disposed.So when I try to look at the feature types again, I get the following error, since the connection is now closed. Hence, all of my ArcSDE feature types no longer show.
2008-08-06 15:05:39,470 WARN [geotools.data] - Could not acquire ESRI(tm) ArcSDE 8.x and 9.x:java.lang.IllegalStateException: The ConnectionPool has been closed.
java.lang.IllegalStateException: The ConnectionPool has been closed.Why is the connecton pool closing immediately after what seems to be a successful connection?
I haven't been able to try a nightly build to see if there are any differences yet.
Any help is appreciated.
Thanks,
Rett--- On Thu, 7/17/08, Saul Farber <saul@anonymised.com> wrote:
From: Saul Farber <saul@anonymised.com>
Subject: Re: Geoserver-users Digest, Vol 26, Issue 19
To: geoserver-users@lists.sourceforge.net, retrobmx63@anonymised.com
Date: Thursday, July 17, 2008, 12:44 PM
Rett,The code for the ArcSDE plugin is a part of GeoTools, and I
believe that geoserver 1.6.4 is based on geoserver 2.4.x, so to track
down the code for the ArcSDE try hitting the geotools project in the
2.4.x branch.As for the dropped ArcSDE connections, I've not seen
that behavior before. Can you try enabling geotools debugging in
geoserver? Use the config->server->log level setting to go to
"verbose debugging" and see if there are any exceptions right before the connection
pool closed error.Gabriel: is this the "dispose() -> close
pool" error in a released version?Rett: Can you try a geoserver nightly build? See if the
arcsde nightlry + geoserver nightly combo works better for you.--saul
I am using GeoServer 1.6.4 with the ArcSDE Extension.
I seem to be having an odd connection issue.
I am able to connect to ArcSDE but it does not lastlong and it drops the connection.
I can successfully add ArcSDE as a DataStore. And when
I look at the FeatureType drop down list I initially see the
ArcSDE FeatureTypes. But if I start to click on other links
on the admin page and go back to the FeatureType listing,
the ArcSDE FeatureTypes are missing.I checked the geoserver.log to find
"The ConnectionPool has been closedjava.lang.IllegalStateException: The ConnectionPool has been
closed" (ArcSDEConnectionPool.java:229)I do not believe it's my pool parameters that is
causing the issue.
pool.minConnections = 2
pool.maxConnections = 6
pool.timeOut = 500I would like to debug the issue to see why the
connection drops by looking at the source code (line 229),
but was only able to find source code for GeoServer. None of
the extensions seem to have source code accompanying it.Is the source code available? And is anyone having
these dropped connection problems?
Thanks,
Rett