Hi Mike:
The diagnostic line is in version 4.2.4, apparently not in 4.2.2. We are
scrambling to fix a problem in 4.2.4, I will notify you as soon as its
working. That version (4.2.4) probably fixes the error you are seeing,
but in any case the diagnostics should help.
On 3/1/2011 2:51 PM, Mike Berkley wrote:
Thanks, John.
0. Good question, but yes I restarted TDS after changing threddsConfig.xml
1. serverStartup.log references OpendapServlet initialization, but
does not contain anything about ascLimit or binLimit:
2011-03-01T13:14:50.201 -0800 [ 27459][ 5] serverStartup:
thredds.server.opendap.OpendapServlet initialization start -
Non-request thread opening.
2011-03-01T13:14:50.201 -0800 [ 27459][ 5] serverStartup:
thredds.server.opendap.OpendapServlet initialization done -
Non-request thread closing - 0
2. Spelling check is correct, although I did use bigger values (10000
and 1000000 respectively).
<Opendap>
<ascLimit>10000</ascLimit>
<binLimit>1000000</binLimit>
<serverVersion>opendap/3.7</serverVersion>
</Opendap>
I introduced an error on purpose (finLimit instead of binLimit), and
there was no error message about finLimit either.
yes that would silently fail.
BTW, those are Mbytes so 1000000 Mb = 1 Tb.
