Hi, I am the developer. Can you set the log level in geoserver to finest, reproduce the error, zip the log file and send it to me.
Additionally attach your xml config file. Christian Quoting Mathieu Lavoie <[email protected]>: > Hi, > > I try to use the Image Mosaic JDBC plugin with the OS OpenData 1:250 > 000 Scale Colour Raster data available from > http://www.ordnancesurvey.co.uk/oswebsite/products/250kraster/ > > > I've followed the steps from Geoserver to create the tiles and > pyramids: > http://docs.geoserver.org/stable/en/user/tutorials/imagemosaic-jdbc/imagemosaic-jdbc_tutorial.html > > The tiles and pyramids were created successfully as well as the DB import. > > Now, when I create the data store, I'm getting the following error: > > Feb 9, 2011 5:11:17 PM > org.geotools.gce.imagemosaic.jdbc.JDBCAccessBase > calculateExtentsFromDB > INFO: Calculate extent for Coverage: osm:tileosm_0:tileosm_0 > Feb 9, 2011 5:11:18 PM > org.geotools.gce.imagemosaic.jdbc.JDBCAccessBase > calculateExtentsFromDB > INFO: Calculate extent for Coverage: osm:tileosm_0:tileosm_0 > finished in 31 ms > Feb 9, 2011 5:11:18 PM > org.geotools.gce.imagemosaic.jdbc.JDBCAccessBase > calculateExtentsFromDB > INFO: Calculate extent for Coverage: osm:tileosm_1:tileosm_1 > Feb 9, 2011 5:11:18 PM > org.geotools.gce.imagemosaic.jdbc.JDBCAccessBase > calculateExtentsFromDB > INFO: Calculate extent for Coverage: osm:tileosm_1:tileosm_1 finished in 0 ms > Feb 9, 2011 5:11:18 PM > org.geotools.gce.imagemosaic.jdbc.JDBCAccessBase > calculateExtentsFromDB > INFO: Calculate extent for Coverage: osm:tileosm_2:tileosm_2 > Feb 9, 2011 5:11:18 PM > org.geotools.gce.imagemosaic.jdbc.JDBCAccessBase > calculateExtentsFromDB > INFO: Calculate extent for Coverage: osm:tileosm_2:tileosm_2 finished in 0 ms > Feb 9, 2011 5:11:18 PM > org.geotools.gce.imagemosaic.jdbc.JDBCAccessBase > calculateResolutionsFromDB > INFO: Calculate resolutions for Coverage: osm:tileosm_0:tileosm_0 > Feb 9, 2011 5:11:18 PM > org.geotools.gce.imagemosaic.jdbc.JDBCAccessBase getPixelResolution > WARNING: Image IO cannot read from ByteInputStream,use less > efficient jai methods > Feb 9, 2011 5:11:18 PM > org.geotools.gce.imagemosaic.jdbc.ImageMosaicJDBCReader <init> > SEVERE: null > Feb 9, 2011 5:11:18 PM > org.geotools.gce.imagemosaic.jdbc.ImageMosaicJDBCFormat getReader > WARNING: null > java.io.IOException > at > org.geotools.gce.imagemosaic.jdbc.ImageMosaicJDBCReader.<init>(ImageMosaicJDBCReader.java:157) > at > org.geotools.gce.imagemosaic.jdbc.ImageMosaicJDBCFormat.getReader(ImageMosaicJDBCFormat.java:199) > at > org.geotools.gce.imagemosaic.jdbc.ImageMosaicJDBCFormat.getReader(ImageMosaicJDBCFormat.java:63) > at > org.geoserver.catalog.ResourcePool.getGridCoverageReader(ResourcePool.java:972) > at > org.geoserver.catalog.CatalogBuilder.buildCoverage(CatalogBuilder.java:623) > at > org.geoserver.web.data.layer.NewLayerPageProvider.getItems(NewLayerPageProvider.java:86) > > > I've tried Geoserver 2.0.2, 2.0.2 nightly build and 2.1.0 RC1 with > the same result. > > Then, if I try Save the store again, the "Calculate extent for > Coverage: osm:tileosm_0:tileosm_0" takes forever to complete (> 30 > min) and then fail with the same error. > > any thoughts on this error? > > > Thanks > > Mathieu > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
