Geoserver becomes unresponsive after idle time

GeoServer GeoServer User
1

Hi Everyone,

 We have a Geoserver 2.24.2 deployed as a docker image in our Kubernetes environment and have multiple pods running (3 at a given time).

We have two applications connect to Geoserver in their backend to fetch and load Layers in their UI.

From users, we have received multiple complaints sayings, layers are becoming un responsive after they leave their systems idle to get some coffee or go for a walk.

In the web.xml, i have set the session timeout to 480 Mins.

Currently we are unable to resolve this issue.

Please share if anyone have any idea on this or how to approach it.

Thanks in advance.

With best regards,
Karthikeyan

2

Hi,

It could be that Kubernetes takes down your Geoserver instance. GeoServer demands some memory. If your Kubernetes settings for memory isn’t sufficient it might restart GeoServer, and then the first user will experience some lag before he gets the next response.

Regards,
Roar Brænden

3

Hi Roar,

Thanks for your inputs.

During monitoring, we could see the Geoserver pods uses only half of the memory configured to them.
We use CAS in our Geoserver instance for 2 of our applications to connect with Geoserver in the backend.
Is there any option available to extend the CAS SSO session timeout?

With best regards,
Karthikeyan