With both jdbcstore and hz-cluster installed, I am getting some critical failures revolving around com.hazelcast.nio.serialization.HazelcastSerializationException: There is no suitable serializer for class org.geoserver.platform.resource.ResourceNotification
If I try to update a Resource in JDBCStore using a PUT, I get a HTTP 500 response, but the resource gets updated successfully. Looking in the logs, I see the following error:
If I try to edit a layer and enable the UTFGrid format on the Tile Caching tab, when I try and save the layer the save fails and I get the following error:
In both these cases, it looks like Hazelcast is trying (and failing) to serialize org.geoserver.platform.resource.ResourceNotification (which is presumably being produced by jdbcstore), causing an exception. Given the mixed behavior I am seeing (sometimes the action works despite the exception), it seems like GeoServer is not expecting a exception to be thrown from the places this exception is being thrown.