Hi,
Taking a look at the code and looking on the JIRA history, I have found
GEOT-4533 which has been fixed by forcing the Automatic mixed mode[1] to be
set as default connection parameter:
The key point when following the step outlined by Just to remove the GWC
specific jars is to first stop the container altogether. Then you remove the
jars. Otherwise, GeoServer won't start again. Maybe evident to Java-developers,
but it wasn't to me a few weeks back when I tried the same...
W dniu 10.02.2016 o 11:27, Rahkonen Jukka (MML) pisze:
> Hi,
>
> I would have a try with selecting all layers from the Tile Caching –
> Tile Layers page and doing “Remove selected cached layers”
Or try this solution:
Hi,
I would have a try with selecting all layers from the Tile Caching – Tile
Layers page and doing “Remove selected cached layers”
-Jukka Rahkonen-
Chris Brown wrote:
We've recently switched to using the external GWC. The problem is that we have
lots of layers that were created using whilst
We've recently switched to using the external GWC. The problem is that we
have lots of layers that were created using whilst we were using the
internal GWC and they are all still caching tiles even though they aren't
being used.
Is there anyway to stop GWC working for all layers even if they had
