Ciao John, this should not happen unless you manulally dumped the gdal-geotiff jar from imageio-ext yourself into GeoServer. That file is not part the gdal extension ( I checked :) ).
I would do this, I would remove that JAR from geoserver and change this one line in the mosaics properties: SuggestedSPI=it.geosolutions.imageioimpl.plugins.tiff.TIFFImageReaderSpi this would tell the mosaic to use the standard pure java TIFF reader. Regards, Simone Giannecchini == Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information. == Ing. Simone Giannecchini @simogeo Founder/Director GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 333 8128928 http://www.geo-solutions.it http://twitter.com/geosolutions_it ------------------------------------------------------- On Tue, Nov 5, 2013 at 5:29 PM, John Callahan <john.calla...@udel.edu> wrote: > I believe the problem is fixed but wanted to describe it to the list in case > an alternate fix would have been more appropriate. > > I am serving raster data using both the ImagePyramid and ImageMosaic > plugins. Mostly GeoTiffs. I am also using the integrated GWC and for the > most part, things have been working well for the past few months using > GeoServer 2.4 RC1. > > When I upgraded to 2.4.1 last week, one of my layers using ImagePyramid > (with GeoTIFFs as the data source) would not render. GWC cached images > displayed fine but once I went deeper into the imagery where cached images > didn't exist, the following error would appear: > > org.geotools.data.DataSourceException: java.lang.ClassNotFoundException: > it.geosolutions.imageio.plugins.geotiff.GeoTiffImageReaderSpi > > > To fix it, I copied imageio-ext-gdalgeotiff-1.1.7.jar from the 2.4 RC1 > installation into the 2.4.1. Apparently, this file was not included in 2.4.1 > or the GDAL extension. My guess is that this one particular layer was > using the GDAL GeoTiff driver back in 2.4 RC1 but in 2.4 GeoServre was > trying to use the native (non-GDAL) GeoTiff driver. I probably could have > deleted the later and created it again. However, I didn't want to change > the layer settings if I could help it. It seems this issue may occur again > during the next upgrade. Does this make sense? > > - John > > > John Callahan > Research Scientist > Delaware Geological Survey > University of Delaware > http://www.dgs.udel.edu > john.calla...@udel.edu > > > ------------------------------------------------------------------------------ > November Webinars for C, C++, Fortran Developers > Accelerate application performance with scalable programming models. Explore > techniques for threading, error checking, porting, and tuning. Get the most > from the latest Intel processors and coprocessors. See abstracts and > register > http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk > _______________________________________________ > Geoserver-users mailing list > Geoserver-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-users > ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
