Justin Deoliveira ha scritto: > Ok, thanks for the explanation. So my guess is one of two thing: > > 1. Either datastore is being disposed but client code is still holding > onto it. In which case its being disposed prematurely. Or: > > 2. The resource cache is holding onto stale entries in the when as you > say, it should be clearing them out. > > Scheduling a jira to look into this for 1.7.1. Unless you feel its > serious enough to schedule it sooner? > > http://jira.codehaus.org/browse/GEOS-2278
If it's easily reproduced I'd say it's a blocker for 1.7.0, we cannot tell people to restart geoserver every time the make a config change. I'll have a look and see if I can reproduce it. 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
