|
|
|
Issue Type:
|
 Bug
|
|
Affects Versions:
|
2.1.4
|
|
Assignee:
|
Daniele Romagnoli
|
|
Components:
|
Configuration
|
|
Created:
|
17/Jul/12 4:03 AM
|
|
Description:
|
See the following trace:
at java.util.concurrent.ThreadPoolExecutor.setMaximumPoolSize(ThreadPoolExecutor.java:1450)
at org.geoserver.coverage.CoverageAccessInitializer.initCoverage(CoverageAccessInitializer.java:94)
at org.geoserver.coverage.CoverageAccessInitializer$1.handleGlobalChange(CoverageAccessInitializer.java:51)
at org.geoserver.config.impl.GeoServerImpl.fireGlobalModified(GeoServerImpl.java:168)
at org.geoserver.config.impl.DefaultGeoServerFacade.save(DefaultGeoServerFacade.java:60)
at org.geoserver.config.impl.GeoServerImpl.save(GeoServerImpl.java:139)
at org.geoserver.config.UpdateSequenceListener.incrementSequence(UpdateSequenceListener.java:40)
at org.geoserver.config.UpdateSequenceListener.handlePostModifyEvent(UpdateSequenceListener.java:59)
at org.geoserver.catalog.impl.CatalogImpl.event(CatalogImpl.java:1192)
at org.geoserver.catalog.impl.CatalogImpl.firePostModified(CatalogImpl.java:1169)
at org.geoserver.catalog.impl.DefaultCatalogFacade.saved(DefaultCatalogFacade.java:834)
at org.geoserver.catalog.impl.DefaultCatalogFacade.save(DefaultCatalogFacade.java:771)
at org.geoserver.catalog.impl.CatalogImpl.save(CatalogImpl.java:1092)
The event handling code does not check what properties were modified, as a result the update sequence increment update happening at every change in the configuration results in a reload of the coverage settings…
|
|
Fix Versions:
|
2.1.5
|
|
Project:
|
GeoServer
|
|
Priority:
|
 Major
|
|
Reporter:
|
Andrea Aime
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your [JIRA administrators](https://jira.codehaus.org/secure/ContactAdministrators!default.jspa).
For more information on JIRA, see: [http://www.atlassian.com/software/jira](http://www.atlassian.com/software/jira)