Re: [Geoserver-users] Catalog initialization slow

Mark I tried creating a GEOMETRY_COLUMNS table as you had suggested. Unfortunately there is no performance gain from doing that. It uses that new table rather than the oracle user_sdo_geom_metadata table, but still does an open connection, query, then close connection for each layer. I was

Re: [Geoserver-users] Catalog initialization slow

Op wo 4 apr. 2018 20:28 schreef Robertafoster8 : > Thanks Mark for the reply and suggestion - I will try adding the > GEOMETRY_COLUMNS table as you suggested. > > Any thoughts on having the initialization been kicked off when the > GeoServer > war is deployed? I was

Re: [Geoserver-users] Catalog initialization slow

Thanks Mark for the reply and suggestion - I will try adding the GEOMETRY_COLUMNS table as you suggested. Any thoughts on having the initialization been kicked off when the GeoServer war is deployed? I was thinking of tying a rest call in the init() section of a servlet filter. Bob -- Sent

Re: [Geoserver-users] Catalog initialization slow

2018-03-29 1:44 GMT+02:00 Robertafoster8 : > I have a GeoServer 2.9.4 configuration with about 150 layers that use an > Oracle spatial database. They use a oracle JNDI data store. I have > GeoServer deployed in a weblogic cluster using the same data directory and > no

[Geoserver-users] Catalog initialization slow

I have a GeoServer 2.9.4 configuration with about 150 layers that use an Oracle spatial database. They use a oracle JNDI data store. I have GeoServer deployed in a weblogic cluster using the same data directory and no tile cache. Each layer used a view in oracle. When the war is deployed the