Fix startup failures with jdbcconfig #262
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
groldan
force-pushed
the
bug/jdbcconfig_startup_failure
branch
from
2aa5a14 to
d3900b0
Compare
JDBCDirectoryStructure gets its cache only from DefaultCacheProvider.findProvider(). Unfortunately there's no sane way of disabling it other than setting the default provider to no-op cache. And it is necessary because the resources in the cache will never be up to date with the database contents, which prevents starting up from an empty database, since all instances will think the geoserver security manager resources are uninitialized and hence try to upgrade the configuration;
groldan
force-pushed
the
bug/jdbcconfig_startup_failure
branch
from
8407a79 to
572651a
Compare
groldan
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JDBCDirectoryStructureJDBCDirectoryStructuregets its cache only fromDefaultCacheProvider.findProvider().Unfortunately, there's no sane way of disabling it other than setting the
default provider to no-op cache.
And it is necessary because the resources in the cache will never be up
to date with the database contents, which prevents starting up from an
empty database, since all instances will think the geoserver security
manager resources are uninitialized and hence try to upgrade the
configuration;