[Geoserver-devel] [JIRA] (GEOS-10423) NullPointerException: GWC Layer MISS

Sander Mol created an issue

GeoServer / BugGEOS-10423

NullPointerException: GWC Layer MISS

Issue Type:

BugBug

Affects Versions:

2.20.2, 2.20.3

Assignee:

Unassigned

Attachments:

geoserver-error.log

Components:

GWC

Created:

16/Mar/22 2:33 PM

Priority:

MediumMedium

Reporter:

Sander Mol

Problem

Whenever I request a tile that is not cached (geowebcache-cache-result: MISS), I get a null pointer exception without a geowebcache-miss-reason header.

URL: https://<redacted-geoserver-url>/geoserver/ows/wms/?SERVICE=WMS&VERSION=1.3.0&REQUEST=GetMap&FORMAT=image/png&TRANSPARENT=true&LAYERS=<redacted-layer-name>&WIDTH=256&HEIGHT=256&CRS=EPSG:4326&STYLES=&BBOX=51.94061279296875,5.086669921875,51.943359375,5.08941650390625&exceptions=application/json

After a second run, and the tile is cached (geowebcache-cache-result: HIT), I no longer get this error in GeoServer.

Set up

The GWC set up uses “direct WMS integration” and uses “no explicit TILED parameter”.

Error

Full logs as an attachment.

> 6 Mar 13:06:13 ERROR [org.geoserver.ows] -
> java.lang.NullPointerException
> at org.geoserver.gwc.wms.CachingWebMapService.invoke(CachingWebMapService.java:76)
> at org.geoserver.gwc.wms.CachingWebMapService.invoke(CachingWebMapService.java:41)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> at org.geoserver.ows.util.RequestObjectLogger.invoke(RequestObjectLogger.java:51)
> at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186)
> at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:212)


Please let me know if more information is needed. To me, it looks like the missing geowebcache-miss-reason header might be related to the actual problem, but I am unsure how to debug this further.

Add Comment

Add Comment

Get Jira notifications on your phone! Download the Jira Cloud app for Android or iOS


This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100197-sha1:e769b43)

Atlassian logo