Geoserver 2.25.2 layergroup not showing up in GetCapabilities

GeoServer GeoServer User
,
1

Hi,

I have a question regarding layer groups.

I work with a Geoserver version 2.25.2 that is installed on a Windows server.

I created the layer group A that contains 5 layers. The layer group A works fine in the Layer Preview. I checked the WMS GetCapabilities and the layer group was available. Then I opened QGIS (version 3.28.4) and I saw that I could download the layer group A as a WMS from my Geoserver and again everything was fine.

I needed a new layer group that I named B. Layer group B is composed of some layers and layer group A. Again, everything is fine in the Layer Preview for both layer group A and B.

Now if I check the WMS GetCapabilities, the layer group A has disapeared. When I connect Qgis to the WMS service of my Geoserver, the layer group A is no longer available too.

I deleted the layer group B and now the layer group A is available again in the WMS GetCapabilities.

I don’t know if a known bug or if it’s a setting that must be changed ? It is really necessary that both layer groups A and B are available in the WMS GetCapabilities

I previously used a Geoserver (version 2.7.1) and I never had this problem.

Thanks in advance
Maxime

2

Hi Maxime

I am not sure if it is a bug or not, but I can suggest that you take a look at Layer Group modes Layer Groups — GeoServer 2.26.x User Manual which sounds like it is playing a role in your config.

Peter

3

Hi Peter,

The documentation helped but I don’t understand how the Geoserver 2.25.2 behaves compared to the Geoserver 2.7.1. In the version 2.7.1, all our layer groups were set to single mode. If I do that in the version 2.25.2, it does not behave the same way.

I switched my layer group B from single mode to Named Tree. I can now download the layer group A that is inside my layer group B as a WMS layer
using QGIS. It fixed part the of the problem.

Thanks you
Maxime

4

@Maxime this is good feedback, and may be a regression. Let’s compare the two branches and see if anything changed with layer group.

I am going to share my research here incase others need an example:

  1. Release notes are here: Release GeoServer 2.25.2 · geoserver/geoserver · GitHub

    I do not see anything that about layer group the above release notes.

  2. Because GeoServer makes a tag standalone, not part of a branch it is hard to compare between two tags.

a) 2.25.2 history shows 06f15aca7f2eea2004299f460b944d59b83552bc is the commit just before the tag.

b 2.25.1 history shows 36fe72f3d8c0335330acada14bf31eeee47743cc the commit just before the 2.25.1 tag

So the compare is: Comparing 36fe72f3d8c0335330acada14bf31eeee47743cc..06f15aca7f2eea2004299f460b944d59b83552bc · geoserver/geoserver · GitHub

Actually now that I read those docs 2.25.2^ is a short cut for “one commit before”.

So this works also: Comparing 2.25.1^..2.25.2^ · geoserver/geoserver · GitHub

We have a winner - there are some changes to WMS 1.3.0 Capabilities to do with reporting errors or skipping misconfigured things.

  • GEOS-11280 Short-circuit request processing upon ClientStreamAbortedException when SKIP_MISCONFIGURED_LAYERS is true

@groldan was responsible for this one, and although it is marked resolved, it did not indicate the version so it was not included in the release notes.

Thanks for reporting this problem clearly, so we could figure out there is an issue. I am going to reopen this ticket and we can work with Gabe to see what happened.

5

@jive you’re comparing 2.25.2 against 2.25.1 whereas the report mentions 2.7.1, a much older version.

Can we first confirm which version we’re talking about?

Cheers

6

Oh … wow. @Maxime is updating from 2.7.1:

I previously used a Geoserver (version 2.7.1) and I never had this problem.

That is like from 2015… Looking at GetCapabilitiesTransformer history there is a lot more then just the most recent optimization from Gabe.

Options:
a) The usual procedure here is to update a major release a time, testing as you go… this is generally good advice.

b) However - as we are seeking a specific problem you could do a “binary search testing” to quickly locate the problem.

Test 2.16 which is halfway between 2.7 and 2.25…

  • If it does not have the problem, update to 2.20 and test again
  • If it has the problem, we know it occurred before, downgrade to 2.12 and test again

This way in only a few iterations you can identify when the problem was introduced.

7

Hi @jive and @groldan ,

Yes the version 2.7.1 is pretty old hahaha.

I spoke to my boss and unfortunately, I cannot do the testing that you suggested. You can consider that the problem is solved.

I will keep in mind everything you said next time we update our Geoserver.

Thanks a lot for your advice.
Have a nice day
Maxime