Some spatial operations can take a very long time to execute and if the user creates a large selection and attempts to perform one of those operations against the selection this could result in high CPU usage for an extended period while the operation is performed. Usually, the browser has timed out before the operation completes and, making matters worse, the user may re-try the operation causing even more load to be placed on the server.
To try and mitigate this risk, Weave implements a limit on the number of entities that can be selected before one of these operations is performed. The default for this limit is 200 but can be changed by setting a system property named weave.spatial.operation.limit
to the new limit, or 0
to disable it.
Create a step-by-step guide:
..\weave\service\conf\wrapper.conf
and add an additional system propertywrapper.java.additional.## = ...
-Dweave.spatial.operation.limit=###
###
is the new value you want to use for the limit (or 0
)startup.cmd
or startup.sh
to start Weave then you need to do the same thing for those files but the way the properties are set is differentJAVA_OPTS
variable must be updated.wrapper.java.additional.22 = -Dweave.spatial.operation.limit=500 |
|
|
The content by label feature displays related articles automatically, based on labels you choose. To edit options for this feature, select the placeholder below and tap the pencil icon.
|