[Geoserver-users] GeoServer 2.21-M0 milestone available for feedback.

Hi Jody,

I updated my test server from 2.20 to 2.21-M0 using the Windows installer. Basically logging worked, but I’m seeing less logging entries now for the DEFAULT_LOGGING configuration. For example, I’m missing the

2022-04-26 13:46:57,820 INFO [org.geoserver] - Loaded data store ‘***’, enabled

2022-04-26 13:46:59,413 INFO [org.geoserver] - Loaded feature type ‘***’, enabled

2022-04-26 13:46:59,429 INFO [org.geoserver] - Loaded layer ‘***’

2022-04-26 13:47:00,070 INFO [org.geoserver] - Read catalog in 3.422 s

2022-04-26 13:47:00,148 INFO [org.geoserver] - Loaded service ‘WMTSInfoImpl–44f35506:159d0de9a1e:-7fff’, disabled

entries after restarting the service. Is this intentional behaviour?

Sending the log output to a location outside of the GeoServer installation directory did work as before.

My previous *.properties configuration files have been deleted by the installer, which I had changed to reflect my needs (which maybe I shouldn’t have done??)

Changing the new *.xml configuration files didn’t work because they are reset to default after restarting the service. But this isn’t a problem because I was able to recreate my previous configuration (simple RollingFile appender with TimeBasedTriggeringPolicy) in a new profile xml file.

Switching between profiles works seamlessly without the need to restart the service.

Best regards

Daniel

···

Jody Garnett

That is somewhat expected; they should be CONFIG level logging now. We can adjust CONFIG messages to be shown as part of DEFAULT_LOGGING if they are of interest to you.

If you wish to try that out, may a copy of DEFAULT_LOGGING.xml and adjust the geoserver loggers to “config” level.

The same approach works for your previous properties files - to preserve any customizations make a copy with a new name. You should still be able to use the log4j 1.2 properties files configurations with this upgrade (indeed it would be great if you could test this as it is a completely different configuration loader). I experimented with only replacing DEFAULT_LOGGING.properties → DEFAULT_LOGGING.xml if I could recognize that no customizations had been made, but this check was removed in favour of just upgrading based on feedback in GeoServer meeting.

Thanks for the useful feedback!

Jody

···


Jody Garnett