[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #KDX-923886]: This NcML URL works in 4.2, not in 4.3



> I was using our Matlab NCTOOLBOX, which calls netcdf-java under the hood.
> 
> >> url='http://geoport.whoi.edu/thredds/dodsC/usgs/data0/bathy/lidar/me/maine_geo.ncml'
> 
> url =
> 
> http://geoport.whoi.edu/thredds/dodsC/usgs/data0/bathy/lidar/me/maine_geo.ncml
> 
> >> nc=ncgeodataset(url)
> Error using ncdataset (line 91)
> Failed to open 
> http://geoport.whoi.edu/thredds/dodsC/usgs/data0/bathy/lidar/me/maine_geo.ncml
> 
> Error in cfdataset (line 55)
> obj = address@hidden(url);
> 
> Error in ncgeodataset (line 20)
> obj = address@hidden(url);
> 
> Caused by:
> Java exception occurred:
> java.io.IOException: Server returned HTTP response code: 400 for URL:
> http://geoport.whoi.edu/thredds/dodsC/usgs/data0/bathy/lidar/me/maine_geo.ncml
> 
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown
> Source)
> 
> at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown
> Source)
> 
> at org.apache.xerces.impl.XMLVersionDetector.determineDocVersion(Unknown
> Source)
> 
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> 
> at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
> 
> 
> On Tue, Jun 19, 2012 at 6:08 PM, Unidata THREDDS Support
> <address@hidden> wrote:
> > Hi Rich,
> >
> > Yes, our handling of URLs where we don't know the service type depends on 
> > the order in which we try different services on that URL and how we handle 
> > exceptions on those attempts. Looks like our latest and greatest broke the 
> > OPeNDAP URL that ends in ".ncml" case.
> >
> > I've added this as a JIRA issue here:
> >
> > https://www.unidata.ucar.edu/jira/browse/TDS-295
> >
> > I saw the same 400 response behavior in the ToolsUI Viewer but didn't get 
> > an Exception trace. What method are you using to open this URL in 
> > netCDF-Java?
> >
> > Thanks,
> >
> > Ethan
> >
> > Rich Signell wrote:
> >> This DAP URL
> >> http://geoport.whoi.edu/thredds/dodsC/usgs/data0/bathy/lidar/me/maine_geo.ncml
> >> from datasetScanned NcML file works fine in NetCDF Java 4.2, but in
> >> netcdf 4.3, gives:
> >>
> >> java.io.IOException: Server returned HTTP response code: 400 for URL:
> >> http://geoport.whoi.edu/thredds/dodsC/usgs/data0/bathy/lidar/me/maine_geo.ncml
> >> Â at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown 
> >> Source)
> >> Â at 
> >> com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(Unknown
> >>  Source)
> >> Â at 
> >> com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(Unknown
> >>  Source)
> >> Â at 
> >> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
> >>  Source)
> >> Â at 
> >> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown
> >>  Source)
> >> Â at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown 
> >> Source)
> >> Â at 
> >> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown 
> >> Source)
> >> Â at 
> >> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown
> >>  Source)
> >>
> >> It seems that
> >> dods://geoport.whoi.edu/thredds/dodsC/usgs/data0/bathy/lidar/me/maine_geo.ncml
> >> works in 4.3, so perhaps just reinstate the logic that allowed "http"
> >> prefix to work via OPeNDAP with .ncml" suffix.
> >
> > Ticket Details
> > ===================
> > Ticket ID: KDX-923886
> > Department: Support THREDDS
> > Priority: Normal
> > Status: Closed
> >
> 
> 
> 
> --
> Dr. Richard P. SignellÂÂ (508) 457-2229
> USGS, 384 Woods Hole Rd.
> Woods Hole, MA 02543-1598
> 
> 
Rich,

I was going through cleaning up our e-support tickets and came across this one. 
 The JIRA bug ticket that Ethan opened up was addressed by John and was closed 
back in June.  Have you seen this issue again since then?

-Lansing

Ticket Details
===================
Ticket ID: KDX-923886
Department: Support THREDDS
Priority: Critical
Status: Open


NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.