I tested starting with -Dorg.geoserver.render.raster.direct.disable=true. Unfortunately, I don’t see a change and the problem persists.
Cheers, James From: Andrea Aime <[email protected]> Sent: August 14, 2019 02:26 To: Jody Garnett <[email protected]> Cc: James Rapaport <[email protected]>; [email protected] Subject: Re: [Geoserver-users] WMS requests fail in some instances On Wed, Aug 14, 2019 at 12:04 AM Jody Garnett <[email protected]<mailto:[email protected]>> wrote: 1. I think I know where you’re going with this one, because I thought I had seen something in my earlier testing but I was unable to confirm it. I’ve now tested with different datasets that are geographically further apart. In short, when I make a request to draw in the centre, approximately, of the raster (specifically the group layer extent) the problem occurs. When I make a request to draw towards the edge of the raster the request is successful and the problem does not occur. This indicates to me that the "fast path" is indeed having a failure, which we can report. I agree with Andrea - thanks for the detailed testing. Hmm... might be, but does not fit with how I know the fast path works: it kicks in when there is a single raster source layer, and not smart enough to figure out a layer is out of bounds (generally speaking the rendering does not trust the source bounds, they are quite often out of whack) Cheers Andrea == 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. ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.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 [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
