We can remove that jar in the next version of GeoServer, 2.23.x, because at that point we won't be supporting JDK 8 anymore (JDK 11 already ships with a version of Marlin).
Cheers Andrea On Fri, Sep 2, 2022 at 1:07 PM Hans Yperman <hans.yper...@vliz.be> wrote: > A small JDK17 bug in geoserver: JDK17 already contains the marlin > renderer, so the geoserver marlin conflicts. As a result, when you click > on Server status > Status > List available fonts, you get a crash. There > is probably more impact, but I can’t really tell the difference with or > without marlin. > > > > Solution for me was to remove the marlin-*.jar in WEB-INF/lib > > > > *Hans Yperman* > > Department IT > > IT staff > > *Vlaams Instituut voor de Zee vzw* > > InnovOcean site, Wandelaarkaai 7 > > 8400 Oostende, België > > > > T +32 (0) / M +32 (0) > > *www.vliz.be <http://www.vliz.be>* > > <https://www.vliz.be/> > > > > > > *From:* Andrea Aime <andrea.a...@geosolutionsgroup.com> > *Sent:* woensdag 3 augustus 2022 9:59 > *To:* Hans Yperman <hans.yper...@vliz.be> > *Cc:* geoserver-users@lists.sourceforge.net > *Subject:* Re: [Geoserver-users] Geoserver 2.21.0 and JDK17 > > > > 8 hours load test sounds good, looks pretty stable. > > About performance, yes, I did run some quick benchmarks when JDK 17 came > out, I could not spot a statistically valid difference between > > OpenJDK 17 and an OpenJDK 8 equipped with the Marlin renderer. > > > > Cheers > > Andrea > > > > On Wed, Aug 3, 2022 at 9:45 AM Hans Yperman <hans.yper...@vliz.be> wrote: > > Andrea, > > > > While not production, I’ve cloned our existing geoserver 2.12 to a new > development environment, ubuntu 22 LTS + Tomcat 9 + JDK17, and ran a few > load tests (8+ hours per run) and side by side tests based on the real > production access logs. All seems well. LDAP gave some trouble while > migrating, so I just rebuilt it. Performance is a bit better, but that > might as well be because other parts of the system got upgraded. > > > > Hans > > > > *From:* Andrea Aime <andrea.a...@geosolutionsgroup.com> > *Sent:* dinsdag 2 augustus 2022 10:18 > *To:* Mark Hammond <mark.hamm...@bto.org> > *Cc:* geoserver-users@lists.sourceforge.net > *Subject:* Re: [Geoserver-users] Geoserver 2.21.0 and JDK17 > > > > I confirm what others say, JDK 17 support and Jakarta EE support are two > separate things. > > > > GeoServer would also not work on Tomcat 10, for the same reason, an > application can only > > support J2EE, or Jakarta EE, but cannot support both, the day we switch > GeoServer will > > stop working on older containers. > > > > I'd like to stress another bit, as the documentation states, quoting: "Running > on Java 17 (experimental!) > <https://docs.geoserver.org/latest/en/user/production/java.html#running-on-java-17-experimental> > ". > > I'm not aware of anyone running GeoServer on Java 17 in production, if you > try that, please > > let us know how it goes (after you switch to a J2EE compatible container). > > > > Cheers > > Andrea > > > > > > On Mon, Aug 1, 2022 at 3:23 PM Mark Hammond <mark.hamm...@bto.org> wrote: > > Hi Folks, > > Have been successfully using Geoserver for a number of years. > > Have been doing preparatory work to upgrade to JDK17/Glassfish 6.x > > Having noticed Geoserver 2.21.0 supports JDK17, downloaded this to try > on the new setup. > > Geoserver 2.21.0 fails to deploy on a virgin JDK17/GF6.2.5 setup with > the following error reported in the log: > > remote failure: Error occurred during deployment: Exception while > loading the app : java.lang.IllegalStateException: > ContainerBase.addChild: start: org.apache.catalina.LifecycleException: > java.lang.IllegalArgumentException: java.lang.NoClassDefFoundError: > javax/servlet/ServletContextListener. Please see server.log for more > details. > > This suggests some component within 2.21.0 has not been upgraded to > JDK17 since it is still using the javax.servlet namespace. Tried with > and without additional database drivers/plugins > > Are there separate JDK17 and non-JDK17 branches? If so, where can I > get the JDK17 version from. If there are not separate branches. Can > anyone suggest a set of steps that would see 2.21.0 deploy correctly? > > > Kindest Regards > Mark > > > _______________________________________________ > 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 > > > > > -- > > 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 339 8844549 > > > > 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 > > > > > -- > > 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 339 8844549 > > > > 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 > -- 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 339 8844549 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
_______________________________________________ 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
