You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, when creating a Vert.x application from https://start.vertx.io/ and deploying to Kubernetes, the following error is received:
SEVERE: Failed to create the vert.x instance
java.lang.IllegalStateException: Failed to create cache dir: /tmp-bf04be10-bf2a-455f-b49b-c133796d22b2
at io.vertx.core.file.impl.FileCache.setupCacheDir(FileCache.java:59)
at io.vertx.core.file.impl.FileCache.setupCache(FileCache.java:29)
at io.vertx.core.file.impl.FileResolver.(FileResolver.java:65)
at io.vertx.core.impl.VertxFactory.createFileResolver(VertxFactory.java:164)
at io.vertx.core.impl.VertxFactory.vertx(VertxFactory.java:78)
at io.vertx.core.Vertx.vertx(Vertx.java:86)
Apparently, adding the following property -Dvertx.disableFileCPResolving=true to the Java Optionsfixes the issue.
Modifying the temporary directory location configuration solves the problem.
In Vert.x v4 there is no subdirectory created, the configuration is used as a prefix instead /tmpbf04be10... as opposed to /tmp/bf04be10... which produced the aforementioned issue.
Changing this configuration to something like /tmp/vertx-cache fixes the issue and doesn't break compatibility with v3.
It will also preserves the Cache ClassPath resolution features
Port inference is something that could be improved too. Still need to find best approach for Vanilla Vert.x projects.
As for the port inference, there is not an easy way to infer the exposed ports since in many cases ports are assigned programmatically.
There's already some sort of integration with Vert.x Config and properties files that we may need to revisit in the future.
Description
Current Vert.x support implementation works with
io.reactiverse
Vert.x Maven Plugin, or with Vanilla Vert.x < 4.However, when creating a Vert.x application from https://start.vertx.io/ and deploying to Kubernetes, the following error is received:
Apparently, adding the following property-Dvertx.disableFileCPResolving=true
to the Java Options fixes the issue.Modifying the temporary directory location configuration solves the problem.
In Vert.x v4 there is no subdirectory created, the configuration is used as a prefix instead
/tmpbf04be10...
as opposed to/tmp/bf04be10...
which produced the aforementioned issue.Changing this configuration to something like
/tmp/vertx-cache
fixes the issue and doesn't break compatibility with v3.It will also preserves the Cache ClassPath resolution features
Port inference is something that could be improved too. Still need to find best approach for Vanilla Vert.x projects.
Expected behavior
Vert.x Web
The text was updated successfully, but these errors were encountered: