On 26-10-2020 13:13, Victor.Sinceac wrote:
Hi,

Got error:
/*Value too long for column GRIDSET_ID VARCHAR(32): 'WGS 84 / UTM Zone 34N (EPSG:32634)' (34);*/
in *GeoServer 2.18.0* used with integrated GWC. Full error:

    /Loading quota store failed, the disk quota subsystem is disabled,
    please re-configure: Failed to create or locate tileset
    TileSet[messir:countries_and_water#WGS 84 / UTM Zone 34N
    (EPSG:32634)#image/png#408a9289e97a734867475b5c5178621c355e6e28]
    after 100 attempts; nested exception is
    org.geowebcache.diskquota.jdbc.ParametricDataAccessException: Failed
    to execute statement INSERT INTO TILESET select :key, :layerName,
    :gridSetId, :blobFormat, :parametersId, 0 WHERE NOT EXISTS(SELECT 1
    FROM TILESET WHERE KEY = :key) with params: {blobFormat=image/png,
    gridSetId=WGS 84 / UTM Zone 34N (EPSG:32634),
    layerName=messir:countries_and_water,
    parametersId=408a9289e97a734867475b5c5178621c355e6e28,
    key=messir:countries_and_water#WGS 84 / UTM Zone 34N
    (EPSG:32634)#image/png#408a9289e97a734867475b5c5178621c355e6e28};
    nested exception is
    org.springframework.jdbc.UncategorizedSQLException:
    PreparedStatementCallback; uncategorized SQLException for SQL
    [INSERT INTO TILESET select ?, ?, ?, ?, ?, 0 WHERE NOT EXISTS(SELECT
    1 FROM TILESET WHERE KEY = ?)]; SQL state [90005]; error code
    [90005]; Value too long for column GRIDSET_ID VARCHAR(32): 'WGS 84 /
    UTM Zone 34N (EPSG:32634)' (34); SQL statement: INSERT INTO TILESET
    select ?, ?, ?, ?, ?, 0 WHERE NOT EXISTS(SELECT 1 FROM TILESET WHERE
    KEY = ?) [90005-119]; nested exception is
    org.h2.jdbc.JdbcSQLException: Value too long for column GRIDSET_ID
    VARCHAR(32): 'WGS 84 / UTM Zone 34N (EPSG:32634)' (34); SQL
    statement: INSERT INTO TILESET select ?, ?, ?, ?, ?, 0 WHERE NOT
    EXISTS(SELECT 1 FROM TILESET WHERE KEY = ?) [90005-119]/


Actually, GeoWebCache has value GIDSET_ID VARCHAR(32) hardocoded (see below), while obviously GeoServer has values with length > 32 chars.
Any idea on how to fix this (without rebulding GeoServer)?

looking at the stack trace it seems to go wrong at the database level, so you might be able to expand the GRIDSET_ID column in the H2 database to a larger value by hand (it seems you need 34 char) or you could create a grid with a few chars less so it just fits.

-M



_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to