[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #STZ-688845]: Thredds - OutOfMemoryError with 2 concurrent requests?

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [THREDDS #STZ-688845]: Thredds - OutOfMemoryError with 2 concurrent requests?
  • Date: Tue, 24 Mar 2015 17:10:33 -0600
Hi Rich,

You're right--for such a request, all of the variables within the dataset will 
be loaded into memory-resident arrays. I'm actually surprised that you saw this 
particular error; when I make very large requests via opendap, I get a message 
like:

Error {
    code = 403;
    message = "Request too big=128191.439424 Mbytes, max=500.0";
};

I'm curious why you're not subsetting your requests--that's a core feature of 
opendap. Also, if you prefer to work with whole files, have you considered 
using the HTTP Bulk File Service [1]?

Cheers,
Christian

[1] 
http://www.unidata.ucar.edu/software/thredds/v4.6/tds/reference/Services.html#HTTP

Ticket Details
===================
Ticket ID: STZ-688845
Department: Support THREDDS
Priority: Normal
Status: Closed