Hi Shawn, the bin with Jetty is meant for quick tests, but not really designed for production, mostly to be small.
We don't have Jetty experts on board, it remained from a decision to have a easy to use setup made something like 15 years ago. If you, or anyone else, can contribute fixes to it, they are most welcomed, config files are here: https://github.com/geoserver/geoserver/tree/master/src/release/jetty Production wise, my company deploys on Tomcat exclusively, using the war files, unless the customer insists on something else... I also think core devs have not done deploys in a long while, companies have grown, devops people work on them... I did not keep track, but if I had to guess, the last deploy I actually did myself is easily five years old now :-D So, expertise welcomed, we're also looking for someone to restore the windows installer btw, and maybe the OSX one too. Cheers Andrea On Thu, Apr 16, 2020 at 12:51 AM Shawn <[email protected]> wrote: > Good afternoon everyone, > > I was recently working on getting https working with geoserver 2.16.0 > (comes packaged with jetty.version 9.4.18.v20190429). > > As soon as you enable the https module in the start.ini file, it fails to > start with the following error: > > /usr/lib/jvm/jre-1.8.0/bin/java -server -Xms16G -Xmx16G -Xmn2G -XX: > +UseG1GC -DSTOP.PORT=8079 -DSTOP.KEY=geoserver -jar start.jar 2020-04-14 > 22:12:01.961:WARN:oejx.XmlConfiguration:main: > java.lang.IllegalStateException: No constructor class. > org.eclipse.jetty.server.ServerConnector([],{}) in file:/opt/software/etc/ > jetty-https.xml Caused by: java.lang.IllegalStateException: No constructor > class org.eclipse.jetty.server.ServerConnector([],{}) in > file:/opt/software/etc/jetty-https.xml > > > From talking to developers of jetty, they believed it was a result of > using older etc/ files from a previous jetty version with the current > version packaged. > > I managed to get the https working by copying jetty-https.xml, > jetty-ssl.xml, jetty-ssl-context.xml from the appropriate version geoserver > is packaged with into the etc/ directory delivered by the geoserver > package. I was then able to finish configuring geoserver for https via the > embedded jetty provided. > > I wrote a stackoverflow question regarding this and plan to update it with > an answer as well: > Jetty https module causing startup to fail > https://stackoverflow.com/q/61220799/5637073 > > > Figured I would bring it up to this distro so hopefully a bug can be > written and the files ultimately updated so future out of the box > deployments can easily support https for other users. I think I just "did > enough" to get the https components working as a few other files appeared > to have other updates for the version packaged that were missing from the > geoserver package. > _______________________________________________ > 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 > > > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users > -- Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 http://www.geo-solutions.it 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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
