Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[backport 1.8.x] Fix for GWC not storing tiles when using datadir or jdbcconfig catalog back-ends #512

Merged

Conversation

groldan
Copy link
Member

@groldan groldan commented Sep 9, 2024

backport #511 to 1.8.x


Abstract out the PgconfigGwcInitializer as AbstractGwcInitializer and refactor the default configuration classes to include the initializer.

Tiles weren't being stored when using the datadir or jdbcconfig catalog backends because ConfigurableBlobStore.setChanged() wouldn't be called at startup and it would hence bypass the storage, as its internal configured flag was not set.

…g back-ends

Abstract out the PgconfigGwcInitializer as AbstractGwcInitializer and
refactor the default configuration classes to include the initializer.

Tiles weren't being stored when using the `datadir` or `jdbcconfig`
catalog backends because `ConfigurableBlobStore.setChanged()` wouldn't
be called at startup and it would hence bypass the storage, as its
internal `configured` flag was not set.
@groldan groldan added the bug Something isn't working label Sep 9, 2024
@groldan groldan self-assigned this Sep 9, 2024
@groldan groldan merged commit be71697 into geoserver:release/1.8.x Sep 9, 2024
2 checks passed
@groldan groldan deleted the bug/default_gwc_cache_dir_1.8.x branch September 9, 2024 21:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant