Where can I configure the maximum number of threads that are used when a seed tiles request is used? The default seems to be 16

enter image description here

3 Answers 3


The web interface of GWC seems to use name "task" where it probably should be "thread". Task means a job that aims at seeding the area of the given bounding box and it can use one or more threads.

enter image description here

Anyway, the documentation in http://geowebcache.org/docs/current/webinterface/seed.html and http://geowebcache.org/docs/current/webinterface/seed.html is correctly speaking about threads.

The default number of threads for a task is 1 and it can be set with the drop down menu item which has misleading title "number of tasks to use" or through the REST API. The same misleading name "task" appears on the status page which looks like this when 1 task is running with 4 threads.

enter image description here

Your screen capture informs that you have started 19 separate tasks, each of them running in one thread. All seeding requests have just been started because time counters are in Estimating status. I suppose that you have started the tasks with REST.

As far as I know it is not possible to limit the number of concurrent tasks and threads in GeoWebCache but it accepts all new requests even if there are already lots of old tasks running. That can make the whole service to stuck.

  • True, there's a vocabulary confusion. I want to limit the number of tasks that are run. I run a script on regular basis and I want to limit the number of concurrent tasks to 5 to avoid flooding the server Jun 16, 2017 at 7:34
  • 1
    It would be nice to have a task queue system in GeoWebCache. At the moment I fear that you must implement that by yourself. As a starting point you can make a REST query and check how many active tasks and threads there are.
    – user30184
    Jun 16, 2017 at 8:16

The real answer is, you can't. Because of this.

Geoserver uses an instance of custom Executor class, and this instance is created as Spring Bean in a geowebcache-core-context.xml file. When you download geoserver.war it's buried in a gs-gwc-<version>.jar inside WEB-INF\lib directory.

So the options are:

  1. Submit a PR to GeoServer and GeoWebCache repositories.
  2. Fork the whole thing and build GeoServer for your needs yourself.

As per user30184's answer, the script doing the (re)seed calls has to send them in a delayed mode to make sure all the tasks are not run at once.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.