[thredds] All thredds/opendap request give error-code until thredds-restart?

We have just updated thredds to the latest version 4.0.25. We use thredds to serve different experimental files and aggregations of those as opendap stream.

Yesterday, we experienced a crash of all opendap-request, resulting in:

Error {
    code = 500;
    message = "11";
};

The log-file gives:

java.lang.ArrayIndexOutOfBoundsException: 11
        at ucar.ma2.ArrayInt.getInt(ArrayInt.java:283)

Please find attached the log-file. The first file crashing can be found at:

http://thredds.met.no/thredds/dodsC/nordic4b/mipom_nordic4.an.20090722.nc.html

Afterwards, all opendap requests below http://thredds.met.no/thredds gave the same result, all other requests seemed to be fine. Stopping and Restarting thredds from the tomcat manager reenable opendap.


Best regards,

Heiko

--
Dr. Heiko Klein                              Tel. + 47 22 96 32 58
Development Section / IT Department          Fax. + 47 22 69 63 55
Norwegian Meteorological Institute           http://www.met.no
P.O. Box 43 Blindern  0313 Oslo NORWAY

Attachment: threddsServlet.log.2009-08-21-10.gz
Description: GNU Zip compressed data

  • 2009 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the thredds archives: