[Geoserver-users] GeoServer 2.21-RC available for testing!

GeoServer GeoServer User
1

The GeoServer 2.21http://geoserver.org/release/2.21-RC/-RC Release Candidate is available for testing, see release announcement for a tour of what is new, improved and fixed!

  • Feature Type Customization - one of my favourite features has returned from GeoServer 1 much improved with ability to dynamically generate attributes!

  • A language chooser has been added! / Un sélecteur de langue a été ajouté !

  • You can now define styles for SINGLE or OPAQUE layer groups (each style can gather together the content and styling needed to produce the correct visual)

  • GeoPackage WMS and WFS Output (for WPS output we recommend the WPS Downloader extension)

  • Log4J update, along with Logging REST API and user interface control of request logging.
    The log4j upgrade supported by activity sponsors opengeogroep.nl, www.terrestris.de, how2map.com, www.geonovation.nl

  • WPS KML input/output

  • GDAL 3.x compatibility for those using gdal bridge

Thanks to Jody Garnett (GeoCat) for working on this release, and to everyone who has contributed to what is a fantastic update :slight_smile:

Helping test a release candidate is your chance to contribute directly providing testing and feedback on new functionality (and double checking if your favourite bug is fixed.)

We ask everyone (individuals, organizations, service providers) to:

  1. Download the release candidate
  2. Test with your own data
  3. Reply to this email (even just to say hi)

Participating in testing release candidates is a key expectation of our open source social contract.

  • Helping test is the minimal price of admonition for GeoServer, don’t be cheap share your time!

  • It also just makes good risk management sense; help making a stronger GeoServer

  • We make an effort to thank each person who tests in our release announcement and project presentations.

  • GeoServer commercial service providers are fully expected to test on behalf of their customers.

···

–
GeoServer Project Steering Committee

2

Hi,

just replaced version 2.20.4. I use Geoserver e.g. to display https://github.com/geosolutions-it/osm-styles.
So far I have not noticed any errors. Everything works great. Thank you!

G. Weickelt

3

Did the same thing: replacing 2.20.4 with 2.21-RC.
All works fine. Many thanks.

Stefan

Am 10.05.2022 um 07:34 schrieb Georg Weickelt:

Hi,

just replaced version 2.20.4. I use Geoserver e.g. to display https://github.com/geosolutions-it/osm-styles.
So far I have not noticed any errors. Everything works great. Thank you!

G. Weickelt

_______________________________________________
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

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--
Dipl. Ing. Stefan Overkamp
overkamp@anonymised.com
https://mapstore.geodaten-velbert.de

4

Hi Jody,

I upgraded my test installation from 2.20.4 to 2.21-RC using the windows installer. Everything works fine, including the Oracle-, Monitor- and GeoFence-Plugins. I changed the logging configuration like discussed with the 2.21-M0 release (DirectWriteRolloverStrategy/TimeBasedTriggeringPolicy) and logging works like expected, but I still have to set the full absolute path to the log folder in the FilePattern option (however this isn’t a problem in my environment).

Regards

Daniel

···

From: Jody Garnett [mailto:jody.garnett@…84…]
Sent: Tuesday, May 10, 2022 6:13 AM
To: GeoServer Users geoserver-users@lists.sourceforge.net
Subject: [EXTERN!]: [Geoserver-users] GeoServer 2.21-RC available for testing!

The GeoServer 2.21http://geoserver.org/release/2.21-RC/-RC Release Candidate is available for testing, see release announcement for a tour of what is new, improved and fixed!

· Feature Type Customization - one of my favourite features has returned from GeoServer 1 much improved with ability to dynamically generate attributes!

· A language chooser has been added! / Un sélecteur de langue a été ajouté !

· You can now define styles for SINGLE or OPAQUE layer groups (each style can gather together the content and styling needed to produce the correct visual)

· GeoPackage WMS and WFS Output (for WPS output we recommend the WPS Downloader extension)

· Log4J update, along with Logging REST API and user interface control of request logging.
The log4j upgrade supported by activity sponsors opengeogroep.nl, www.terrestris.de, how2map.com, www.geonovation.nl

· WPS KML input/output

· GDAL 3.x compatibility for those using gdal bridge

Thanks to Jody Garnett (GeoCat) for working on this release, and to everyone who has contributed to what is a fantastic update :slight_smile:

Helping test a release candidate is your chance to contribute directly providing testing and feedback on new functionality (and double checking if your favourite bug is fixed.)

We ask everyone (individuals, organizations, service providers) to:

  1. Download the release candidate

  2. Test with your own data

  3. Reply to this email (even just to say hi)

Participating in testing release candidates is a key expectation of our open source social contract.

· Helping test is the minimal price of admonition for GeoServer, don’t be cheap share your time!

· It also just makes good risk management sense; help making a stronger GeoServer

· We make an effort to thank each person who tests in our release announcement and project presentations.

· GeoServer commercial service providers are fully expected to test on behalf of their customers.

–

GeoServer Project Steering Committee

5

Thanks Daniel, going to open a bug report about requiring the full absolute path (as that would be a regression).

https://osgeo-org.atlassian.net/browse/GEOS-10487

I had a much simpler test changing the log location to “logs/GeoServer.txt” and being ignored.

···

–
Jody Garnett

6

Reporting back with some of my own testing:

···

–
Jody Garnett

–
GeoServer Project Steering Committee

7

Tried the RC, works as expected, see comments in the ticket: https://osgeo-org.atlassian.net/browse/GEOS-10443

Cheers
Andrea

···

GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail

8

Thanks Andrea, it was user error on my part (running locally without checking all the right dependencies in IDE).

···

–
Jody Garnett

GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail

9

Hi Jody,
I was debugging some JAI code and think I’ve found a regression (but I’m not 100% sure).
I’m dealing with a case where an exception is thrown in JAI code, and even setting the logging level to “VERBOSE”,
the JAI errors are not getting logged… and I believe they were, before (this is the part I’m not 100% sure about).

The imaging listener does not seem to have been touched during the Log4J2 refactor:
https://github.com/geoserver/geoserver/blob/7c52ac99e607e84294c8de40f1ad403753e930e6/src/main/src/main/java/org/geoserver/GeoserverInitStartupListener.java#L95

Thinking out loud:

  • Timing issue? The logger is likely grabbed before the logging can be initialized
  • Configuration issue? Maybe the log profiles used to load the “javax.media.jai” package and now they don’t anymore
    Jody, does this ring a bell to you?

Cheers
Andrea

···

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail

10

Andrea:

I did run into these kind of issues where loggers created too soon were set up with a java util logger before we could get in there and supply a logging factory. I found the ‘easiest’ way to trace the problem was to put in a breakpoint where the logger was created (and trace back to see the responsible code).

I tried using a JAI_LOGGING.xml based on GEOTOOLS_LOGGING.xml and adding the following. I did not see any java.media.jai messages.

I am not sure if their is a regression here or not, Do you have a reliable way to make a JAI exception?

···

–
Jody Garnett

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

http://twitter.com/geosolutions_it

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail