Justin Deoliveira ha scritto: > Hmmm... problematic definitely. It could be that the datastore disposal > still has a few bugs in it. On 1.7.x that is now managed by the > ResourcePool class. > > I am not familiar with the connection pooling stuff that much. Should a > connection pool be around for the life of the application and something > independent of datastore disposal? If i remember properly the datastore > factory creates a pool? SO i guess the answer is no. > > I wonder if a datastore is being disposed but the application still has > reference to one...
DataStore.dispose() says that once it's called, you should not use anymore the datastore nor any of the objects created thru it. May it be that the datastore is disposed, but some feature sources are kept around? As for the connection pool lifespan, the way we do things it's that the pool dies along with the datastore. To have an application long pool we should allow the usage of JNDI based ones, there are patches floating around but I never found the time to commit them (patches with no unit tests, I need to create them before commit). Long story short, resource pool should probably wipe out all of its caches when datastores get disposed. Mind, this is just a hunch, I did not actually try to reproduce or debug this one. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------- 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-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
