Thank you, Andrea. I will recreate a small reproduction file as soon as I can. I will be out of the office for the remainder of January, so I might not get to if for a while. Once I do, I will create an issue, as directed by your reply.
Thanks! ~Mike > On Jan 9, 2019, at 5:32 AM, Andrea Aime <andrea.a...@geo-solutions.it> wrote: > > Hi, > see notes inline. > > On Fri, Jan 4, 2019 at 9:01 PM Michael Bronner via Geoserver-users > <geoserver-users@lists.sourceforge.net > <mailto:geoserver-users@lists.sourceforge.net>> wrote: > > I guess that leaves me with a few questions: > > - Would GeoServer crash because of a warning-level issue with the package? > > No, it's not related. Judging by the stack trace, your geopackage is not > "rectangular", some tiles are likely > missing on some side, and this triggered a code path that has never been > tried out before (geopackage support > in GeoServer is new, and the raster part of it in particular it still pretty > green). > > - Is something else at play here, not necessarily related to the package > itself? > > Unlikely > > - Where is this exception logged? (It isn’t being logged to the logs folder > in data_dir.) > > This I don't know, it should be there in the geoserver.log file, unless maybe > a "QUITE" logging profile > has been selected, or some other logging location configured. > > Suggestion: prepare a subset of the geopackage, possibly small, that can > still reproduce the issue, and > open a ticket in Jira. See instructions at > https://osgeo-org.atlassian.net/projects/GEOS/summary > <https://osgeo-org.atlassian.net/projects/GEOS/summary> > > Cheers > Andrea > > == > GeoServer Professional Services from the experts! Visit http://goo.gl/it488V > <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://www.geo-solutions.it/> > http://twitter.com/geosolutions_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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
