Closed andermirik closed 2 years ago
Hi @andermirik
I'm pretty sure the issue is the jdbcconfig backend quickly exhausts the connection pool.
Can you try 1.0-RC17
, and increase the number of connections (at least for the gwc-service) like this in geoserver.yml
:
geoserver:
backend:
jdbcconfig:
datasource:
url: ...
...
minimumIdle: ${jdbcconfig.minConnections:2}
maximumPoolSize: ${jdbcconfig.maxConnections:8}
So at least increase the value of geoserver.backend.jdbcconfig.datasource.maxConnections
, either directly or throuhg the jdbcconfig.maxConnections
environment variable if you're using the default config
(it has to be 1.0-RC17
cause I just fixed the max pool size configuration)
BTW, v1.0-RC21
should fix the (most?) jdbcconfig connection starvation issues, if you dare to try it out. Cheers.
Closing due to lack of feedback. Feel free to reopen it if the problem persists.
profile:
jdbcconfig
request likehttp://localhost:9090/gwc/service/wmts?REQUEST=GetTile&SERVICE=WMTS&VERSION=1.0.0&LAYER=workspace:ne_10m_roads&STYLE=&TILEMATRIX=EPSG:4326:{z}&TILEMATRIXSET=EPSG:4326&FORMAT=application/vnd.mapbox-vector-tile&TILECOL={x}&TILEROW={y}
has execute time is bigger then 5 minutes.part of logs: