As noted here, upgrading the NetCDF library will pose some challenge: https://osgeo-org.atlassian.net/browse/GEOS-10831
See also: * https://osgeo-org.atlassian.net/browse/GEOT-7048 * https://github.com/geotools/geotools/pull/3728 * https://github.com/geotools/geotools/pull/3738 Cheers Andrea Mostra testo citato Il mar 24 gen 2023, 07:42 Jody Garnett <jody.garn...@gmail.com> ha scritto: > I expect we will need to wait on netcdf for a fix; thank you for reporting > the issue to them. > -- > Jody Garnett > > > On Fri, Jan 20, 2023 at 3:21 PM Hans Yperman <hans.yper...@vliz.be> wrote: > >> We found a bug where geoserver grows basically unbounded (32GB+) when >> using hdf5, while the java heap and native heaps stay small (2GB and 300MB >> resp). The bug still exists in the current version of netcdf-java. The main >> symptom is unfortunately not noticeable with JVM tooling: a lot of mmapped >> segments of around 64K each appear when you look on linux with pmap. >> >> I hacked a fix in the cdm-4.6.15.jar library. A test scenario that >> crashed the server in minutes now runs for an hour straight without growing >> the process RSS size. >> >> I logged a bug in both projects (the geoserver one is pretty minimal). >> >> https://github.com/Unidata/netcdf-java/issues/1138 >> >> https://osgeo-org.atlassian.net/browse/GEOS-10831 >> >> >> >> >> >> *Hans Yperman* >> >> Department IT >> >> *Vlaams Instituut voor de Zee vzw* >> >> InnovOcean Campus, Jacobsenstraat 1 >> >> 8400 Oostende, België >> >> >> >> ☎+32 (0) 59 33 61 13 >> >> 📧 hans.yper...@vliz.be >> >> *www.vliz.be <http://www.vliz.be>* >> >> >> >> >> _______________________________________________ >> 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 >> > _______________________________________________ > 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 >
_______________________________________________ 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
