Thanks for the advice, Andrea. I found this related ticket in JIRA which was closed as Won't Fix so I'm going to recommend removing the BIL extension and finding another solution.
https://osgeo-org.atlassian.net/browse/GEOS-7319 Jason Newmoyer Newmoyer Geospatial Solutions 843.606.0424 ja...@newmoyergeospatial.com On Tue, Sep 21, 2021 at 3:05 AM Andrea Aime < andrea.a...@geosolutionsgroup.com> wrote: > Hi Jason, > I can't share direct experience about BIL, but the one time I glanced over > the code, it seemed like it was making > GeoServer renders a map in 8 bits, just to throw it away and start over > encoding the raw data [1]. > If anything, that seems inefficient :-D > > If it's a true deadlock, then find out the process id of GeoServer, go to > the command line, > and run: > > jstack pid > > The output should give you an idea of what the JVM threads were doing, and > if there is a true deadlock, it will > also be reported at the end of the output. > > Cheers > Andrea > > > [1]: See > https://github.com/geoserver/geoserver/blob/main/src/community/dds/src/main/java/org/geoserver/wms/worldwind/BilMapResponse.java#L93 > The base class renders an 8bit output image, which is passed to this > method... it happily proceeds to ignore it and then builds a response > starting over from the request object. > > On Tue, Sep 21, 2021 at 2:36 AM Jason Newmoyer < > ja...@newmoyergeospatial.com> wrote: > >> We are using the BIL/DDS extension to provide elevation data through the >> WMS and an ImageMosaic layer of 16 bit geotiffs. >> >> We see GeoServer deadlocking consistently when image/bil GetMap requests >> are being made to the server with large bounding boxes. I believe these are >> errant requests by the client, but instead of having them timeout in the >> worst case, they actually make geoserver unresponsive. Jetty will just >> start returning 404s for everything. Only restarting the service will bring >> it back. >> >> In troubleshooting, we are noticing two things: >> 1) When making GetMap requests with the "image/png" output format, the >> rendering process seems to ignore stylesheets. This is made obvious by the >> scale dependencies we have set in the default style not having any >> effect. 2) Also, setting the "Maximum number of granules to load" >> setting seems to have no effect, which I would typically use a safeguard >> for this type of situation. >> >> Wondering if anyone knows a workaround or does this sound like a bug in >> the WMS rendering path for BIL? >> >> Thank you. >> >> Jason Newmoyer >> Newmoyer Geospatial Solutions >> 843.606.0424 >> ja...@newmoyergeospatial.com >> >> >> _______________________________________________ >> 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 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 >
_______________________________________________ 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
