Has anyone encountered issues with propagating some configuration settings
with JMS Clustering plugin? There are some issues at Geoserver JIRA:
https://osgeo-org.atlassian.net/browse/GEOS-7263
<https://osgeo-org.atlassian.net/browse/GEOS-7263>
https://osgeo-org.atlassian.net/browse/GEOS-7268
<https://osgeo-org.atlassian.net/browse/GEOS-7268>
https://osgeo-org.atlassian.net/browse/GEOS-7269
<https://osgeo-org.atlassian.net/browse/GEOS-7269>
I stll use 2.7.x in production, currently testing 2.9 - still haven't got to
clustering, but from Chris Brown's tests on 2.9 nighty i suppose the issues
are still there. In my case - stores, layers, styles etc... are propagating
instantly, but changes in layergroups or general geoserver settings like
WMS/WFS settings are not propagated to slaves. Shouldn't all changes in data
dir be propagated to slaves?
--
View this message in context: http://osgeo-org.1560.x6.nabble.com/JMS-Clustering-issues-tp5284800.html
Sent from the GeoServer - User mailing list archive at Nabble.com.