|
|
Niels Charlier created an issue |
|
isolated workspace may cause broken links between catalog objects |
|
Issue Type: |
|
|---|---|
|
Assignee: |
|
|
Components: |
Main |
|
Created: |
10/Apr/23 10:35 AM |
|
Priority: |
|
|
Reporter: |
Medium|
The ResolvingProxy object uses the ‘raw’ catalog so it bypasses all security, but the raw catalog does not bypass the isolated workspace catalog facade. As a consequence, if the proxy is resolved as part of a request, it resolves to null when it shouldn’t (for instance, the store of a resource is set to null). This object with broken link is then cached and causes geoserver to be broken. Normally this doesn’t happen, because the isolated facade checks for the existence of a request in the thread and normally the resolving happens outside of a request (when loading geoserver). However, we have a health check that repetitively does GetCapabilities requests and this is causing the problem. In theory it could happen to anyone (the health check may be considered a stress test) |
|
|
|
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#100221-sha1:57945e1) |
|
|
|
