Stefan,
If you can figure out the last imported layergroupinfo, you could check
if it contains a broken reference to a layer or style. It's probably
something like that.
It might be necessary to use a debugger to find out what is going wrong,
unfortunately. As I mentioned in previous email, it is a known issue
that there should be better error reporting during import which could
avoid this in many cases, and make it possible for a regular user to fix
the problem.
Kind Regards
Niels
On 14/05/2020 16:13, Stefan Overkamp wrote:
Hi list,
I'm currently testing jdbconfig (and jdbcstore) as part of having a
multiple geoserver cluster.
Importing the catalog runs fine for all object types except for
org.geoserver.catalog.LayerGroupInfo.
Only 3 to 4 from 27 LayerGroupInfo are imported.
The last LayerGroupInfo logs "Storing properties of
LayerGroupInfoImpl... with pk 832" but this pk can not found in the
object table.
Restarting Geoserver fails, when other configuration like gwc-layers
references LayerGroups which have not been imported.
Removing these references prior to import allows starting geoserver
(with the missing layergroups).
Adding layergroups afterwards is possible.
Adding layergroups to layergroups is not possible. The selection list is
empty.
Has anyone successfully imported layergroups with jdbcConfig?
Thanks
Stefan
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
If you want to request a feature or an improvement, also see this:
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users