Community module: DataDirectory Catalog Loader - problems

Hi Gabe

GeoServer v2.25.3 (oscarfonts docker image)
gs-datadir-catalog-loader-2.25-SNAPSHOT.jar (dated 2024-12-19)

I was testing your DataDirectory Catalog Loader — GeoServer 2.27.x User Manual and it works on 4 of 5 of my GeoServer configs, but there is one that just does not load the catalog at all with this module enabled.

I have produced a diff of the 2 logs files for you to see where the one (indicated with + in column 1) does not load the catalog.

load_diff.log (31.6 KB)

What can I do to help debug this further?

Thanks

Peter

Also replicated on the latest docker release 2.26.1 with https://build.geoserver.org/geoserver/2.26.x/community-latest/geoserver-2.26-SNAPSHOT-datadir-catalog-loader-plugin.zip

I have narrowed the problem down to either the layers’ projection being 404000 (because there is no geometry associated with the layer) or there was no default style associated with the layers. Once fixed, the catalog is loaded successfully with this config.

I can continue to try to produce a test case, if this is of use to you @groldan

Peter

Having dirty data directories is pretty common, the loader should be solid enough to skip over the misconfigured bits. In other terms, it should be able to load what the current loader was loading too.

While testing it some months ago, I’ve experienced a complete lockup of the GeoServer during startup, some comments and a link to a test data directory can be found here:

Wondering if it happens on other machines as well… given the concurrent nature of the loader, it may happen on some hardware, and not on others.

Anyhow, certainly looking forward to have a faster data dir loader!

Cheers
Andrea

Hi,

I’m looking for representative datadir issues that’d trigger these failures.

Besides Peter’s finding about the no-geometry layer, do you have any idea what else might be causing this? @Andrea Aime would you have a data directory to share with me?

TIA,
Gabe

Hem… in the message you quoted there is a link pointing at the data directory… here it is again:

While testing it some months ago, I’ve experienced a complete lockup of the GeoServer during startup, some comments and a link to a test data directory can be found here:
https://github.com/geoserver/geoserver/pull/7421#issuecomment-2296306956

The comment shows the stack traces of the locked up GeoServer, as well as giving a link to the sample data dir, at the end.
In any case, here is a direct link to it.