Hi Steve,
Thanks for information update.
I have experienced the problems except 1 bit image support, with existing
Georaster plugin. Mainly problem with temp table space full and server
restart problem gets high priority. We are restarting geoserver most of the
times (at least once in two days).
I will keep in mind this issues and proceed while configuring georasters.
Any improvements are planned for this ImageMosaicJDBC plugin?
Regards,
Hari.
On Thu, May 26, 2011 at 5:04 PM, Steve Way <
[email protected]> wrote:
> Hi Hari,
>
>
>
> I have to warn you there are quite a few issues with this plugin.
>
>
>
> I started work on improving this but had to scrap as came across too many
> issues, noteably:
>
>
>
> 1) If you run a soak test of requests against raster layers,
> eventually TEMP tablespace will be full and no more requests can happen
> until server restart
>
> 2) Does not support 1 bit images
>
> 3) Several bugs where also noted – connections / resultsets and
> statements being left open etc.
>
> 4) Performance is also an issue
>
>
>
> I have worked with Christian also on Oracle Georaster, and we took another
> approach, one where you can use native SQL to export the image, but this
> will have a limitation on 64mb per tile, or you can use the native oracle
> libraries which does not have a limit per tile and also has great
> performance.
>
>
>
> This works with your use case of retrieving tiles from the DB and
> mosaicking them within the imagemosaic-jdbc module. It has been tested with
> Oracle 10g, not 11g however.
>
>
>
> Contact me if you want any further information.
>
>
>
> Christian – Did you manage to catch up with Simone regarding how we
> progress with this?
>
>
>
> Regards,
>
> Steve
>
>
>
> *From:* Harikumar Reddy [mailto:[email protected]]
> *Sent:* 26 May 2011 12:19
> *To:* [email protected]
> *Cc:* [email protected]
> *Subject:* Re: [Geoserver-users] Georaster & ImagemosaicJDBC jars problem
>
>
>
> Hi Christian,
>
> Baskar has sent java code files, which have to be build and converted to
> jar using maven. We are starting this process today/tomorrow. He has sent a
> document and listed your name (Geotools support) under Acknowledgements
> section in the document.
>
> The results of georaster plugin (they named it as georaster plugin)
> includes the given below advantages as per document (as per my
> understanding).
>
> 1. users can configure more than one georasters in a single XML file
> (more than one means, it can be 100 or more also)
> 2. It has less number of configuration parameters when compared with
> existing georaster XML config file.
> 3. It will automatically mosaic surrounding georasters.
> 4. The plugin doesn't have any dependency on other licensed jars.
>
> We will also check and update feedback to Baskar about this plugin, so it
> can be useful to the GS community.
>
> Regards,
> Hari.
>
>
> On Thu, May 26, 2011 at 3:46 PM, <[email protected]> wrote:
>
> Quoting Harikumar Reddy <[email protected]>:
>
> Hi Christian,
>
> Thankyou for immediate support, may be this is the reason behind
> Geoserver's
> a BIG success as one of the best web map servers today.
>
> Thanks
>
>
>
>
> I have removed the imagemosaicjdbc jar from the geoserver WEB-INF/lib
> folder
> and downloaded and copied again. Restarted our server. It worked. There was
> no change in the jar files version from already implemented system and the
> current new implementation system.
>
>
>
> Just wondering, no idea what could be happened.
>
>
>
>
> java path & other configurations verified and looks ok. Last time it was
> solved due to copy of previous version imagemosaicjdbc (2.0.1 & 2.0.3) &
> other jar files of oracle jdbc (you have specified yesterday too, there is
> an additional ojdbc14_g.jar also copied). It was same implementation we
> were
> already having and working fine.
>
>
>
> The oracle jar files have to be installed manually, this is due to license
> issues.
>
>
>
>
> I found one imteresting document for ImagemosaicJDBC and a team is working
> (CoreLogic, Banglore, India) on extending the existing ImagemosaicJDBC
> version developed by your team. You can find the details in the given url.
> They have described that the latest jar may be checked in soon on geoserver
> repository soon, once they will complete all the tests. The contact
> email-id
> is *[email protected]*
>
>
> http://www.google.co.in/url?sa=t&source=web&cd=10&ved=0CFcQFjAJ&url=http%3A%2F%2Fwww.geospatialworldforum.org%2F2011%2Fproceeding%2Fpdf%2FBaskar.pps&rct=j&q=geoserver%20configuration%20of%20oracle%20georaster&ei=B3PbTbHYCIntrQe55tnoDg&usg=AFQjCNHN96C65xDsFxGwvn8ViCz2czDEoQ&cad=rja
>
> Ahh, Baskar, I can remember I supported him to develop his special
> module. They do not use the tiling feature of Oracle GeoRaster and split
> the image into multiple records. Not sure if this works for any kind of
> image.
>
> Cheers
> Christian
>
>
>
> Regards,
> Hari.
>
>
> On Wed, May 25, 2011 at 8:35 PM, <[email protected]> wrote:
>
> Quoting Harikumar Reddy <[email protected]>:
>
> Hi Christian,
>
>
> Thanks for reply. I got help from you before also, to configure goeraster
> with geoserver and succeeded (problem is i am thinking of consistency).
> But
> i didn't expect that again i will struggle for the same problem...
>
> I have made chages to the
> Settings->Global-->GEOTOOLS_DEVELOPER_LOGGING.properties as per your
> advise.
> i will send the required log of geotools asap after admin is available.
>
> Can you please give little guidance or suitable URL on how to set/check
> the
> jdbc driver classpath on linux, as i am into pure gis domain with windows
> os
> and dont have much linux knowledge.
>
>
> The oracle jar file has to be in
> GEOSERVER_INSTALLATION_DER/WEB-INF/lib
>
> Another possibility is to put the jar in
> lib/ext of your Java installation.
>
> echo $JAVA_HOME
>
> will show you the directory.
>
> At least, you start your java virtual machine with the option
> -verbose:class , you will see the class loading sequence in the log file.
>
> Cheers
>
>
> Thanks,
> Hari.
>
>
> On Wed, May 25, 2011 at 3:01 PM, <[email protected]> wrote:
>
> Hi, I am the developer.
>
> Your config file looks good and yes, the coverageName goes into the id
> column of your record.
> Unfortunately, the stack trace does not show the original exception.
>
> To be sure, the jdbc Driver is in your class path ?
>
> You can configure the log level in geoserver GUI.
> Settings->Global-->GEOTOOLS_DEVELOPER_LOGGING.properties
>
> After a restart, you should see a lot more messages in the log file,
> please
> zip and send to me.
>
>
>
>
>
>
> Quoting Harikumar Reddy <[email protected]>:
>
> Hi GS users,
>
>
> I am verymuch happy with Geoserver performance for vector layers., but
> for
> georaster it is really a problematic configaration.
>
> Is there any possibility to configure oracle georasters which are
> occupying
> bulk disk size...and possibility to access with openlayers api or any
> other
> api (or anyone is using oracle mapviewer and using any oracle map api's
> for
> only georaster). ImagemosaicJDBC is giving problems and no consistent
> solutions to resolve this issues. one of the main problem i am facing
> now
> is
> given below.
>
> Can anyone faced similar problem with ImagemosaicJDBC for Geoserver
> 2.0.2
> version. We have successfully installed and working on test server
> environment, but when tried to do the same implementation in the
> deployment
> environment., ImagemosaicJDBC is giving errors as given below.
>
> are they really format errors or jar mismatch errors. AFAIK,
> ImagemosaicJDBC
> plugin has to be more consistent like vector layers configarations in
> GS.
> This error i have encountered before also and with help of GS users tech
> forum and checking one by one jar files, successfully configured
> (copying
> 2.0.1 & 2.0.3 imagemosaicjdbc jar files in 2.0.2 version has solved my
> problems). This time, tried very much, but not succeeded with this idea.
>
> Could not list layers for this store, an error occurred retrieving them:
> Unable to acquire a reader for this coverage with format:
> ImageMosaicJDBC
>
> The os used is linux centos, with Geoserver 2.0.2 (imagemosaicJDBC
> version
> is also taken correct version)
>
> can anyone explain the parameters <coverageName name="SAT"/> Normally
> this
> value is filled in the ID coloumn record (please correct me if i am
> wrong).
>
> Both environments are same when compared. Why it is giving problem.
>
> The configaration file parameters i am giving below for reference.
>
> ===================================================
> <?xml version="1.0" encoding="UTF-8" standalone="no"?>
> <config version="1.0">
> <coverageName name="SAT"/>
> <coordsys name="EPSG:4326"/>
> <!-- interpolation 1 = nearest neighbour, 2 = bipolar, 3 = bicubic
> -->
> <scaleop interpolation="1"/>
> <spatialExtension name="georaster"/>
> <mapping>
> <masterTable name="GEOR_SAT1" >
> <geoRasterAttribute name="GEORASTER"/>
> <coverageNameAttribute name="ID"/>
> </masterTable>
> </mapping>
> <connect>
> <!-- value DBCP or JNDI -->
> <dstype value="DBCP"/>
> <!-- <jndiReferenceName value=""/> -->
>
> <username value="mytestcon" />
> <password value="mytestcon" />
>
> <jdbcUrl value="jdbc:oracle:thin:@10.0.0.1:1521:test.localdb" />
> <driverClassName value="oracle.jdbc.OracleDriver"/>
> <maxActive value="10"/>
> <maxIdle value="0"/>
> </connect>
> </config>
> =======================================================
>
>
> *The error log is also pasted below.*
>
> 25 May 00:53:32 INFO [geoserver.web] - Getting list of coverages for
> saved
> store file:coverages/geortest/sri1.xml
> java.lang.RuntimeException: Could not list layers for this store, an
> error
> occurred retrieving them: Unable to acquire a reader for this coverage
> with
> format: ImageMosaicJDBC
>
> at
>
>
>
> org.geoserver.web.data.layer.NewLayerPageProvider.getItems(NewLayerPageProvider.java:92)
> at
>
>
>
> org.geoserver.web.wicket.GeoServerDataProvider.getFilteredItems(GeoServerDataProvider.java:162)
> at
>
>
>
> org.geoserver.web.data.layer.NewLayerPageProvider.getFilteredItems(NewLayerPageProvider.java:108)
> at
>
>
>
> org.geoserver.web.wicket.GeoServerDataProvider.size(GeoServerDataProvider.java:177)
> at
>
>
>
> org.geoserver.web.wicket.GeoServerTablePanel$Pager.first(GeoServerTablePanel.java:477)
> at
>
>
>
> org.geoserver.web.wicket.GeoServerTablePanel$Pager.updateMatched(GeoServerTablePanel.java:467)
> at
>
>
>
> org.geoserver.web.wicket.GeoServerTablePanel$Pager.<init>(GeoServerTablePanel.java:442)
> at
>
>
>
> org.geoserver.web.wicket.GeoServerTablePanel.<init>(GeoServerTablePanel.java:188)
> at
>
>
>
> org.geoserver.web.wicket.GeoServerTablePanel.<init>(GeoServerTablePanel.java:82)
> at
> org.geoserver.web.data.layer.NewLayerPage$1.<init>(NewLayerPage.java:95)
> at
> org.geoserver.web.data.layer.NewLayerPage.<init>(NewLayerPage.java:92)
> at
>
>
>
> org.geoserver.web.data.store.CoverageStoreNewPage.onSave(CoverageStoreNewPage.java:71)
> at
>
>
>
> org.geoserver.web.data.store.AbstractCoverageStorePage$1.onSubmit(AbstractCoverageStorePage.java:114)
> at
>
>
>
> org.apache.wicket.ajax.markup.html.form.AjaxSubmitLink$1.onSubmit(AjaxSubmitLink.java:94)
> at
>
>
>
> org.apache.wicket.ajax.form.AjaxFormSubmitBehavior.onEvent(AjaxFormSubmitBehavior.java:128)
> at
>
>
>
> org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:163)
> at
>
>
>
> org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:297)
> at
>
>
>
> org.apache.wicket.request.target.component.listener.BehaviorRequestTarget.processEvents(BehaviorRequestTarget.java:104)
> at
>
>
>
> org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRequestCycleProcessor.java:91)
> at
>
>
>
> org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1239)
> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1316)
> at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1418)
> at org.apache.wicket.RequestCycle.request(RequestCycle.java:532)
> at
>
> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:356)
> at
>
>
>
> org.apache.wicket.protocol.http.WicketServlet.doPost(WicketServlet.java:145)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at
>
>
>
> org.springframework.web.servlet.mvc.ServletWrappingController.handleRequestInternal(ServletWrappingController.java:158)
> at
>
>
>
> org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
> at
>
>
>
> org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
> at
>
>
>
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:875)
> at
>
>
>
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809)
> at
>
>
>
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571)
> at
>
>
>
> org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:511)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at
>
>
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
>
>
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
>
>
>
> org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108)
> at
>
>
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at
>
>
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
>
>
>
> org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:265)
> at
>
>
>
> org.acegisecurity.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:107)
> at
>
>
>
> org.acegisecurity.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:72)
> at
>
>
>
> org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at
>
>
>
> org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124)
> at
>
>
>
> org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at
>
>
>
> org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
> at
>
>
>
> org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at
>
>
>
> org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
> at
>
>
>
> org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at
>
>
>
> org.acegisecurity.wrapper.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:81)
> at
>
>
>
> org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at
>
>
>
> org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
> at
>
>
>
> org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at
> org.acegisecurity.ui.logout.LogoutFilter.doFilter(LogoutFilter.java:110)
> at
>
>
>
> org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at
>
>
>
> org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
> at
>
>
>
> org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275)
> at
>
>
> org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:149)
> at
>
>
>
> org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98)
> at
>
>
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at
>
>
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.geoserver.filters.LoggingFilter.doFilter(LoggingFilter.java:73)
> at
>
>
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at
>
>
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
>
>
>
> org.geoserver.filters.ReverseProxyFilter.doFilter(ReverseProxyFilter.java:183)
> at
>
>
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at
>
>
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at org.geoserver.filters.GZIPFilter.doFilter(GZIPFilter.java:47)
> at
>
>
>
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
> at
>
>
>
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
>
>
>
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
> at
>
>
>
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
> at
>
>
>
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
> at
>
>
>
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
> at
>
>
>
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at
>
>
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
> at
>
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
> at
>
>
>
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
> at
>
>
>
> org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:409)
> at
>
>
>
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
>
>
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: java.lang.Exception: Unable to acquire a reader for this
> coverage
> with format: ImageMosaicJDBC
> at
>
>
> org.geoserver.catalog.CatalogBuilder.buildCoverage(CatalogBuilder.java:577)
> at
>
>
>
> org.geoserver.web.data.layer.NewLayerPageProvider.getItems(NewLayerPageProvider.java:72)
> ... 83 more
>
> 25 May 00:53:32 INFO [geoserver.catalog] - Disposing grid coverage
> reader
> 'sri1'
> 25 May 00:53:32 WARN [geoserver.catalog] - Error occured disposing
> coverage
> reader 'sri1'
>
> Any suggestions on how to resolve this issue...
>
> Many thanks in advance,
> Hari.
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
>
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
>
>
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> ------------------------------
> DISCLAIMER:
>
> This email may contain confidential information and is intended only for
> the use of the specific individual(s) to which it is addressed. If you are
> not the intended recipient of this email, you are hereby notified that any
> unauthorized use, dissemination or copying of this email or the information
> contained in it or attached to it is strictly prohibited. If you received
> this message in error, please immediately notify the sender at Infotech or
> [email protected] and delete the original message.
>
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
