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

[THREDDS #SYD-491615]: TDS java exception "java.lang.NegativeArraySizeException" for large netcdf

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 #SYD-491615]: TDS java exception "java.lang.NegativeArraySizeException" for large netcdf
  • Date: Fri, 25 Apr 2014 16:10:46 -0600
Luke,

I finally got my system back online today.  It's not clear what 
happened, but I had to wipe out and reinstall my standard toolkit 
programs.  I fired up a catalog with your file in it, which is 3.1G in 
size.  I noticed that trying to download the entire dataset through the 
ncss service failed because the maximum size limit in threddsConfig.xml 
is set at the default 52428800 (50 Megabytes).  I upped the maximum size 
by editing this parameter in threddsConfig:

   <NetcdfSubsetService>
     <allow>true</allow>
     <scour>15 min</scour>
     <maxAge>30 min</maxAge>
<!--maxFileDownloadSize>2097152</maxFileDownloadSize-->
<!--maxFileDownloadSize>52428800</maxFileDownloadSize-->
<maxFileDownloadSize>10552428800</maxFileDownloadSize>
   </NetcdfSubsetService>

Then I realized that somehow, the file is being seen as much larger than 
3.1G, which is an odd behavior...I shouldn't have to specify 10G to 
cover a 3.1G file.  So, I'll have to dig and see what's going on.

Have a good weekend,
   Lansing

On 4/11/2014 5:31 PM, Luke Sheneman wrote:
> New Client Reply: TDS java exception "java.lang.NegativeArraySizeException" 
> for large netcdf
>
> Thanks Lansing -
>
> I've attached the latest log files.
>
> I am somewhat familiar with the data.   These are downscaled climate
> model outputs.  Some of the data are historical and some are
> predictive.   The one you were looking at is predicting climate
> scenarios for periods in the future (the years 2086 through 2100).   I
> don't see anything weird with those dates in the data that you were
> looking at...
>
> Have a great weekend, and I look forward to working with you soon to get
> the java exception.
>
> Thanks,
>    -Luke
>
>
> --
>
> Luke Sheneman, Ph.D
> Technology and Data Services Manager
> Northwest Knowledge Network (NKN) / University of Idaho
> http://www.northwestknowledge.net
>
> address@hidden
> Office: 208.885.4228   Mobile: 208.669.2248
>
>
> On 4/11/14, 3:58 PM, Unidata THREDDS Support wrote:
>> baby steps...
>>
>> When you get a moment, could you repeat the log capture procedure?  I'm 
>> about to head out for the day, but I'll pull this up again on Monday.  I 
>> looked at one of the files already, which I downloaded using the http 
>> server.  Are you familiar with the data, by chance?  I notice that the 
>> calendar dates (Gregorian, days since 1901-01-01) are for 2086-2100.  Is 
>> this right, or is something else fishy here?
>>
>> Have a good weekend!
>>
>> -Lansing
>>
>> Ticket Details
>> ===================
>> Ticket ID: SYD-491615
>> Department: Support THREDDS
>> Priority: Normal
>> Status: Open
>>
>
>
>
> Ticket Details
> ===================
> Ticket ID: SYD-491615
> Department: Support THREDDS
> Priority: Normal
> Status: Open
> Link:  
> https://www.unidata.ucar.edu/esupport/staff/index.php?_m=tickets&_a=viewticket&ticketid=23770



Ticket Details
===================
Ticket ID: SYD-491615
Department: Support THREDDS
Priority: High
Status: Open