Hi,

We've just installed JDBCConfig on a large GeoServer deployment with about
40,000 layers. The install web smoothly but we're seeing some very strange
behaviour when we do any updates such as adding layers via the REST API.

All such requests hang the server for around 25 minutes. Turning on the
debugging log, it looks like some process is looping over every single
layer in the catalog. The output in the log looks like this:

*** LOG SNIPPET ***

2015-10-20 13:18:54 UTC DETAIL:  parameters: $1 = '15', $2 = '117', $3 =
'', $4 = '219', $5 = '219'
2015-10-20 13:18:55 UTC LOG:  execute <unnamed>: SELECT now()
2015-10-20 13:18:55 UTC LOG:  execute S_2: select blob from object where id
= $1
2015-10-20 13:18:55 UTC DETAIL:  parameters: $1 = ''
2015-10-20 13:18:55 UTC LOG:  execute <unnamed>: SELECT now()
2015-10-20 13:18:55 UTC LOG:  execute S_11: select id from object where
type_id in ($1) AND (
(
oid IN (SELECT oid FROM object_property WHERE property_type IN ($2) AND
value = $3) /* [ name =  ] */
AND
oid IN (select oid from object_property where property_type in ($4) and
value IS NULL) OR oid NOT  in (select oid from object_property where
property_type in ($5)) /* [workspace.id IS NULL ] */
))
 ORDER BY oid limit 2
2015-10-20 13:18:55 UTC DETAIL:  parameters: $1 = '15', $2 = '117', $3 =
'', $4 = '219', $5 = '219'
2015-10-20 13:18:55 UTC LOG:  execute <unnamed>: SELECT now()
2015-10-20 13:18:55 UTC LOG:  execute S_2: select blob from object where id
= $1
2015-10-20 13:18:55 UTC DETAIL:  parameters: $1 = ''
2015-10-20 13:18:55 UTC LOG:  execute <unnamed>: SELECT now()
2015-10-20 13:18:55 UTC LOG:  execute S_11: select id from object where
type_id in ($1) AND (
(
oid IN (SELECT oid FROM object_property WHERE property_type IN ($2) AND
value = $3) /* [ name =  ] */
AND
oid IN (select oid from object_property where property_type in ($4) and
value IS NULL) OR oid NOT  in (select oid from object_property where
property_type in ($5)) /* [workspace.id IS NULL ] */
))
 ORDER BY oid limit 2

*** LOG SNIPPET ***

If anyone has any ideas about what we may have done wrong or any ideas what
might be causing this it would be hugely appreciated. The closest thing I
could find to this issue was this:
http://comments.gmane.org/gmane.comp.gis.geoserver.user/41076

-- Chris
------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to