Ah, sorry about the wrong link, fix is here <https://github.com/geoserver/geoserver/pull/1819>.
Are there any resource stores other than JDBCStore that also use a notification dispatcher? Torben On Wed, Sep 14, 2016 at 3:03 AM, Niels Charlier <[email protected]> wrote: > HI Torben, > > I can't see your fix (it leads back to the same jira issue), but obviously > ResourceNotification needs to be serializable in order to be published over > a hazelcast cluster. > > This doesn't have anything to do with jdbcstore, other than the fact that > the default FileSystemResourceStore does not use a notification dispatcher > at all (it simply watches the files, and does not need the cluster to > communicate about resource changes). The issue is simply with the > HzResourceNotificationDispatcher, nothing else. > > What surprises me most, is that I did not come across this exception > before, I did make a unit test for HzResourceNotificationDispatcher ??! > > Regards > > Niels > > > On 13-09-16 20:25, Torben Barsballe wrote: > > Hello Neils, > > You did most of the work on JDBCStore, correct? Any insight into GEOS-7740 > <https://osgeo-org.atlassian.net/browse/GEOS-7740>? > > I think I have a fix <https://osgeo-org.atlassian.net/browse/GEOS-7740>, > but I am still not quite sure why the issue was occuring in the first > place. I can't see any specific usage of ResourceNotification in JDBCStore. > > Thanks, > Torben > > >
------------------------------------------------------------------------------
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
