NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Since I've gotten our public THREDDS server running I am having to restart it more often than expected, currently about once every two weeks. Every time I check the error logs I see the same message: java.lang.OutOfMemoryError: Java heap space I have increased the heap space sizes multiple times and am currently running with 4096m of initial space and 16384m of max space. Obviously that is not enough but I would rather not increase it again as this server is running out of unused memory space and just giving the application more memory hasn't worked yet. Having it set at 16G is already high for a Java application, at least from what I can gather from Internet resources, so I am wondering if anyone has any recommendations on what might be done. The server is running Debian 11 and THREDDS 5.6 is running on top of Tomcat 10.1.36 with an upgrade planned to the latest version of Tomcat and a further upgrade in the future to Debian 12. Thanks, Chris Woelkers IT Specialist National Oceanic and Atmospheric Administration Great Lakes Environmental Research Laboratory 4840 S State Rd | Ann Arbor, MI 48108 Office: 734-741-2446 Cell: 734-604-0059 Voice: 734-219-3815
thredds archives: