Hi, I'm not using the specific JDBC version but I have been trying to put my ImageMosaic indexes (the shapefiles) into our Oracle database using 2.12.2.
Long and short of it is that it just will not work and so it seems to me there may be an Oracle bug somewhere. After a couple of weeks trying to work it out I finally gave up and just installed a local copy of Postgres with PostGIS on the servers we host our GeoServer on. It is Open Source and the overhead doesn't seem significant; it has fixed the issue and we are now using ImageMosaic (image files in directory) with Postgres holding the image index table. This appears to be working well and I've shared the local databases with the clusters so I only have two instances. You may find using a local copy of Postgres a more sensible workaround but of course that is completely up to you. Perhaps this comment is of some use if not just to back up the possibility of an undiagnosed issue when using ImageMosaic in Oracle. Cheers, Paul -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: 21 February 2018 17:36 To: [email protected] Subject: Geoserver-users Digest, Vol 141, Issue 57 Send Geoserver-users mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/geoserver-users or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Geoserver-users digest..." Today's Topics: 1. WMS does not deliver jpeg 2000 data since update to geoserver 2.12.0 using the ImageMosaicJDBC Plugin ([email protected]) ---------------------------------------------------------------------- Message: 1 Date: Wed, 21 Feb 2018 17:36:01 +0000 From: <[email protected]> To: <[email protected]> Subject: [Geoserver-users] WMS does not deliver jpeg 2000 data since update to geoserver 2.12.0 using the ImageMosaicJDBC Plugin Message-ID: <81e2d314daa0004c837f08b2f8ca12ae0242332...@rzs-expm-p14024.rz-sued.bayern.de> Content-Type: text/plain; charset="us-ascii" Hi, since upgrade to geoserver 2.12.0 using the ImageMosaicJDBC Plugin our wms layer does not provide jpeg 2000 data. Our raster data store as a pyramid in a oracle database. We use 4 band tiff files for the low and 4 band jpeg 2000 files for the high resolution images. Before update to geoserver 2.12.0 we have no problems, the switch from the tiff to the jpeg 2000 files and back works fine. Actually we using a workaround. We find out, if there an older version of geoserver (2.10 or 2.11) is running in the same tomcat container, everything is fine. But if we stop the older version of geoserver, our wms layer doesn't deliver the jpeg 2000 files ( see the logfile snippets below). Temporary this workaround is ok for us, but not for the long term. Any Ideas? regards, Sebastian Tomcat 8.0.41 Java 1.8.0_111 Linux and Windows 7 logfile, only geoserver 2.12.0 is running: 2018-02-21 18:11:10,729 WARN [imagemosaic.jdbc] - Could not read 914277 from stream, switch to JAI 2018-02-21 18:11:10,729 WARN [imagemosaic.jdbc] - Could not read 914273 from stream, switch to JAI 2018-02-21 18:11:10,763 WARN [imagemosaic.jdbc] - Could not read 914275 from stream, switch to JAI 2018-02-21 18:11:10,796 WARN [imagemosaic.jdbc] - Could not read 914279 from stream, switch to JAI 2018-02-21 18:11:10,796 WARN [imagemosaic.jdbc] - Could not read 914278 from stream, switch to JAI 2018-02-21 18:11:10,828 WARN [imagemosaic.jdbc] - Could not read 914276 from stream, switch to JAI 2018-02-21 18:11:10,938 WARN [lite.gridcoverage2d] - Could not reduce the grid geometry inside the valid area bounds: ReferencedEnvelope[-36.0 : 54.0, -85.0 : 85.0] Grid geometry isGridGeometry2D[GeneralGridEnvelope[0..1464, 0..956], PARAM_MT["Affine", PARAMETER["num_row", 3], PARAMETER["num_col", 3], PARAMETER["elt_0_0", 0.3150763362010388], PARAMETER["elt_0_2", 32555504.087072816], PARAMETER["elt_1_1", -0.31507633619843484], PARAMETER["elt_1_2", 5265164.783295045]]] 2018-02-21 18:11:10,938 WARN [lite.gridcoverage2d] - Could not reduce the grid geometry inside the valid area bounds: ReferencedEnvelope[-36.0 : 54.0, -85.0 : 85.0] Grid geometry isGridGeometry2D[GeneralGridEnvelope[0..1464, 0..956], PARAM_MT["Affine", PARAMETER["num_row", 3], PARAMETER["num_col", 3], PARAMETER["elt_0_0", 0.3150763362010388], PARAMETER["elt_0_2", 32555504.087072816], PARAMETER["elt_1_1", -0.31507633619843484], PARAMETER["elt_1_2", 5265164.783295045]]] logfile, if in the same tomcat container geoserver 2.12.0 and 2.11.0 is running: 2018-02-21 18:13:22,149 WARN [lite.gridcoverage2d] - Could not reduce the grid geometry inside the valid area bounds: ReferencedEnvelope[-36.0 : 54.0, -85.0 : 85.0] Grid geometry isGridGeometry2D[GeneralGridEnvelope[0..1464, 0..956], PARAM_MT["Affine", PARAMETER["num_row", 3], PARAMETER["num_col", 3], PARAMETER["elt_0_0", 0.3150763362010388], PARAMETER["elt_0_2", 32555504.087072816], PARAMETER["elt_1_1", -0.31507633619843484], PARAMETER["elt_1_2", 5265164.783295045]]] 2018-02-21 18:13:22,149 WARN [lite.gridcoverage2d] - Could not reduce the grid geometry inside the valid area bounds: ReferencedEnvelope[-36.0 : 54.0, -85.0 : 85.0] Grid geometry isGridGeometry2D[GeneralGridEnvelope[0..1464, 0..956], PARAM_MT["Affine", PARAMETER["num_row", 3], PARAMETER["num_col", 3], PARAMETER["elt_0_0", 0.3150763362010388], PARAMETER["elt_0_2", 32555504.087072816], PARAMETER["elt_1_1", -0.31507633619843484], PARAMETER["elt_1_2", 5265164.783295045]]] -------------- next part -------------- An HTML attachment was scrubbed... ------------------------------ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ------------------------------ Subject: Digest Footer _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users ------------------------------ End of Geoserver-users Digest, Vol 141, Issue 57 ************************************************ "This e-mail is intended for the named addressee(s) only and may contain information about individuals or other sensitive information and should be handled accordingly. Unless you are the named addressee (or authorised to receive it for the addressee) you may not copy or use it, or disclose it to anyone else. If you have received this email in error, kindly disregard the content of the message and notify the sender immediately. Please be aware that all email may be subject to recording and/or monitoring in accordance with relevant legislation." ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
