Re: [thredds] Thredds Opendap Service ascLimit and binLimit

Hi Ethan,

I have downloaded the source for thredds (tdsSrc-4.1) and did a bit of 
debugging.

I had a look at thredds.servlet.ThreddsConfig and 
thredds.server.opendap.OpendapServlet, and based on the documentation, I 
believe that in thredds.server.opendap.OpendapServlet, the following 3 lines:


    this.ascLimit = ThreddsConfig.getInt("ascLimit", ascLimit);
    this.binLimit = ThreddsConfig.getInt("binLimit", binLimit);
    this.odapVersionString = ThreddsConfig.get("serverVersion", 
odapVersionString);

should read:

    this.ascLimit = ThreddsConfig.getInt("Opendap.ascLimit", ascLimit);
    this.binLimit = ThreddsConfig.getInt("Opendap.binLimit", binLimit);
    this.odapVersionString = ThreddsConfig.get("Opendap.serverVersion", 
odapVersionString);


I did a simple test in thredds.servlet.ThreddsConfig

        rootElem.getChild("Opendap").getChild("ascLimit").getText() returns 
what I have configured in ThreddsConfig.xml, which is exactly what private 
static String getParam(String name) does.

Please find attached the file which I have changed. I would have submitted a 
patch but I couldn't find any repository to apply the patch to. (Didn't find 
any links from http://www.unidata.ucar.edu/projects/THREDDS/tech/TDS.html)


As a result, I believe ThreadsConfig.xml isn't being read, and the default 
values (defValue in thredds.servlet.ThreddsConfig.getInt() ) are being used. 
Changes to these 3 lines allow me to properly "configure" my ascii and binary 
limit.

Regards,



Derrick Wong 
Software Engineer | ASRDC (Australian Spatial Research Data Commons) Project | 
CSIRO

Phone: +61 8 6436 8945
derrick.wong@xxxxxxxx | www.csiro.au
Address: ARRC (Australian Resources Research Centre), 26 Dick Perry Avenue, 
Kensington WA 6151, Australia

PLEASE NOTE 
The information contained in this email may be confidential or privileged. Any 
unauthorised use or disclosure is prohibited. If you have received this email 
in error, please delete it immediately and notify the sender by return email. 
Thank you. To the extent permitted by law, CSIRO does not represent, warrant 
and/or guarantee that the integrity of this communication has been maintained 
or that the communication is free of errors, virus, interception or 
interference.
Please consider the environment before printing this email.


-----Original Message-----
From: Wong, Derrick (CESRE, Kensington) 
Sent: Thursday, 26 August 2010 10:38 AM
To: 'Ethan Davis'; thredds@xxxxxxxxxxxxxxxx
Subject: RE: [thredds] Thredds Opendap Service ascLimit and binLimit

Hi Ethan,

Thank you for your reply.

I am currently running Version 4.1.20100520.1554 - 20100520.1554

I have tested serving a dataset which is about 81576444 (<80mbs) and I still 
get that error.

Regards,

Derrick Wong 
Software Engineer | ASRDC (Australian Spatial Research Data Commons) Project | 
CSIRO

Phone: +61 8 6436 8945
derrick.wong@xxxxxxxx | www.csiro.au
Address: ARRC (Australian Resources Research Centre), 26 Dick Perry Avenue, 
Kensington WA 6151, Australia

PLEASE NOTE 
The information contained in this email may be confidential or privileged. Any 
unauthorised use or disclosure is prohibited. If you have received this email 
in error, please delete it immediately and notify the sender by return email. 
Thank you. To the extent permitted by law, CSIRO does not represent, warrant 
and/or guarantee that the integrity of this communication has been maintained 
or that the communication is free of errors, virus, interception or 
interference.
Please consider the environment before printing this email.


-----Original Message-----
From: thredds-bounces@xxxxxxxxxxxxxxxx 
[mailto:thredds-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Ethan Davis
Sent: Thursday, 26 August 2010 2:32 AM
To: thredds@xxxxxxxxxxxxxxxx
Subject: Re: [thredds] Thredds Opendap Service ascLimit and binLimit

Hi Derrick,

The change you made looks like it should have fixed the problem. A
restart of the TDS should be enough for the changes to take affect. (Of
course, restarting Tomcat will work as well.)

What version of the TDS are you running?

In case it isn't clear, the OPeNDAP size limits do not affect the size
of the datasets that can be served only the size of the data that can be
accessed in a single request. So, if you run into this limit, you can
also try to request a smaller subset of the data.

Ethan

On 8/25/2010 3:20 AM, Derrick.Wong@xxxxxxxx wrote:
> Hi all,
> 
> I am currently trying to serve datasets using Opendap
> (via thredds) and some of my datasets are bigger than
> the default sizes (50asc/500bin)
> 
> I have tried configuring it in threddsConfig.xml but
> I am still
> 
> Getting the following error on my browser:
> 
> Error {
>     code = 403;
>     message = "Request too big=81.0 Mbytes, max=50.0";
> };
> 
> Despite specifying the following:
> 
> <Opendap>
>     <ascLimit>500</ascLimit>
>     <binLimit>500</binLimit>
>     <serverVersion>opendap/3.7</serverVersion>
> </Opendap>
> 
> 
> The logs reads:
> 
> 2010-08-25T17:05:30.130 +0800 [     82496][      18] INFO  - 
> thredds.server.opendap.OpendapServlet - Reject request size = 81.0 Mbytes
> 
> 
> I have tried it on a few datasets, reloading my webapp
> as well as restarting tomcat but to no avail.
> 
> Could someone kindly assist?
> 
> Thanks.
> 
> 
> Derrick Wong 
> Software Engineer | ASRDC (Australian Spatial Research Data Commons) Project 
> | CSIRO

_______________________________________________
thredds mailing list
thredds@xxxxxxxxxxxxxxxx
For list information or to unsubscribe,  visit: 
http://www.unidata.ucar.edu/mailing_lists/

Attachment: OpendapServlet.java
Description: OpendapServlet.java

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