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

vertx throws "IllegalStateException: Failed to create cache dir" though "vertx.disableFileCaching=true" #1931

Closed
m0 opened this issue Apr 10, 2017 · 2 comments

Comments

@m0
Copy link

m0 commented Apr 10, 2017

I am using vertx for a small web service that should run without disk write access.
Sadly vertx insists in having a writeable cache directory though I set "vertx.disableFileCaching=true":
java.lang.IllegalStateException: Failed to create cache dir
at io.vertx.core.impl.FileResolver.setupCacheDir(FileResolver.java:293)
at io.vertx.core.impl.FileResolver.(FileResolver.java:86)
at io.vertx.core.impl.VertxImpl.(VertxImpl.java:175)
at io.vertx.core.impl.VertxImpl.(VertxImpl.java:142)
at io.vertx.core.impl.VertxFactoryImpl.vertx(VertxFactoryImpl.java:42)
at io.vertx.core.Vertx.vertx(Vertx.java:90)
at com.sipgate.litc.HealthService.start(HealthService.java:18)
at com.sipgate.litc.Main.main(Main.java:20)

I had a quick look at FileResolver.java and would expect any cacheFile handling to be skipped when ENABLE_CACHING is false, but as far as I understand the code, the public interface of at least FileResolver would have to change.
Before digging deeper into the code and developing a patch, I would like to know if changing the behaviour to match what I expect, is appreciated.

Do I miss something?

@tsegismont
Copy link
Contributor

tsegismont commented Apr 10, 2017 via email

@m0
Copy link
Author

m0 commented Apr 19, 2017

Oh, obviously I misssed that flag when I looked over the code. Thank's for the fast response! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants