This branch fixes the following issue. In the HDF5RequestHandler the DAP response methods utilize a top level try block and the following catch pattern:
This is problematic because the code being run throws various children of BESError, these errors are being swept up in the (...) clause and turned into BESInternalFatalErrors even when they are not fatal errors. Adding this solves the problem nicely:
This branch fixes the following issue. In the HDF5RequestHandler the DAP response methods utilize a top level try block and the following catch pattern:
This is problematic because the code being run throws various children of BESError, these errors are being swept up in the
(...)
clause and turned into BESInternalFatalErrors even when they are not fatal errors. Adding this solves the problem nicely:The affected methods are:
HDF5RequestHandler::hdf5_build_das()
HDF5RequestHandler::hdf5_build_data()
HDF5RequestHandler:: hdf5_build_data_with_IDs()
HDF5RequestHandler::hdf5_build_dds()
HDF5RequestHandler::hdf5_build_dmr()
HDF5RequestHandler::hdf5_build_dmr_with_IDs()