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.
Hi Luke: There are likely error messages in threddsServlet.log in content/thredds/logs Can you find them and send to us? These logs rollover every hour, so make sure the log includes one of the failures. thanks. John > Hi Luke, > > I'm pulling down the new files now. Can you send me your current > catalog.xml and threddsConfig.xml files? I'll throw everything back in > the debugger. > > Thanks, > Lansing > > On 5/20/2014 6:55 PM, Luke Sheneman wrote: > > New Client Reply: TDS java exception "java.lang.NegativeArraySizeException" > > for large netcdf > > > > > > Hi Katherine - > > > > I was looking at THREDDS today and started poking around with your new > > test files. Basically none of your new test files work with OPeNDAP in > > THREDDs. > > > > The test files are here: > > > > http://thredds1.nkn.uidaho.edu:8080/thredds/catalog/NWCSC_INTEGRATED_SCENARIOS_ALL_CLIMATE/macav2livneh/TEST/catalog.html > > > > Some observations: > > > > 1) the first file seems to be artificially truncated at 2.647GB > > (macav2livneh_nocompress_tasmax_CSIRO-Mk3-6-0_historical_1980_1989_CONUS.nc) > > > > > > THREDDs throws this exception when trying to access it via OPeNDAP: > > > > Error { > > code = 500; > > message = "java.io.IOException: File is truncated should be= > > 5981730804 actual = 2647130112"; > > }; > > > > > > > > All of the other files all seem to generate one of two THREDDs Java > > exceptions: > > > > java.lang.NegativeArraySizeException > > java.lang.OutOfMemoryError: Java heap space > > > > I just doubled the memory I allocate for thredds using these start > > params: -Xmx16384m -Xms16384m > > > > But it looks like things are still broken. Again, this looks like a > > problem with THREDDs itself or a problem with how you are generating the > > NetCDFs. The fact that one can open these NetCDFs in other tools > > seems to indicate to me that this is a problem with THREDDs itself. > > > > I will focus on this for the remainder of the week, and hopefully we can > > make some headway. > > > > > > 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 Ticket Details =================== Ticket ID: SYD-491615 Department: Support THREDDS Priority: Emergency Status: Open