[Geoserver-users] Bug: WMS service time out when the logging profile is not set to Production, Quiet or Test

GeoServer GeoServer User
1

Hi,

I’d like to report a strange behavior in my Geoserver instance (v2.15.0):

Setup:

  • GeoServer 2.15.0 running in an Azure App Service on the Microsoft Azure Cloud

Problem:

  • If the logging profile in the Global configuration page is not set to Production, Quiet or Test, I can’t preview or access any layer using the WMS service. I’m getting: “Error 500: The request timed out. The web server failed to respond within the specified time.” which from what I’ve gathered looks like an error from Microsoft Azure when a request does not send back data after a certain time.
  • My WFS service works fine for all the layers. I’m also able to retrieves the WMS GetCapabilities XML.

Any idea what would cause this behavior ? Could it be a problem with the type of file the logger is writing ?

Thanks

Kevin

2

Hi,

if you put the logging in verbose mode, what do have have in log files when
it a request times out ?

--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html