-
Notifications
You must be signed in to change notification settings - Fork 625
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
[IO performance] setDefaultUseCaches(false) impacts all URL connections #656
Labels
Comments
FYI this was done as part of #578 IIRC |
|
Anyone willing to submit a PR for this? |
Opened a PR. |
gotson
pushed a commit
that referenced
this issue
Jul 29, 2022
Use of setDefaultUseCaches impacts all URLClassLoaders and HttpURLConnections, which can lead to erratic behavior of non-sqlite components running on a system since the variable is static. Closes: #656
This is available in the latest snapshot, please give it a try. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using setDefaultUseCaches(false) impacts all URL connections.
Because defaultUseCaches is static (see setDefaultUseCaches implementation).
Maybe you should use setUseCaches instead.
For example, after
setDefaultUseCaches(false)
, each time a new class is loaded from a signed JAR, initializeVerifier is recomputed.Regards.
The text was updated successfully, but these errors were encountered: