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

Add Support for io.vertx:vertx-core:4.3.5 #117

Closed
linghengqian opened this issue Nov 19, 2022 · 4 comments
Closed

Add Support for io.vertx:vertx-core:4.3.5 #117

linghengqian opened this issue Nov 19, 2022 · 4 comments
Labels
enhancement New feature or request

Comments

@linghengqian
Copy link
Contributor

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

  • Add Support for io.vertx:vertx-core:4.3.5.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

  • Null.

Additional context
Add any other context or screenshots about the feature request here.

@linghengqian linghengqian added the enhancement New feature or request label Nov 19, 2022
@linghengqian
Copy link
Contributor Author

linghengqian commented Nov 19, 2022

@linghengqian
Copy link
Contributor Author

  • I know that vertx-core itself has GraalVM reachability metadata, but I really don't understand a series of errors around io.vertx.core.Vertx#clusteredVertx(VertxOptions options, Handler<AsyncResult<Vertx>> resultHandler) . I would first investigate Add support for Hazelcast #32.
11月 21, 2022 7:41:36 下午 io.vertx.core.impl.launcher.commands.RunCommand
严重: Failed to load or instantiate the isolated deployer
java.lang.ClassNotFoundException: io.vertx.core.impl.launcher.commands.VertxIsolatedDeployer
        at [email protected]/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:52)
11月 21, 2022 7:41:36 下午 com.hazelcast.config.XmlConfigBuilder
严重: Failed to parse the inputstream
Exception: Stream closed
11月 21, 2022 7:41:36 下午 io.vertx.core.impl.VertxImpl
严重: Failed to initialize clustered Vert.x
com.hazelcast.config.InvalidConfigurationException: Stream closed
        at com.hazelcast.config.XmlConfigBuilder.parse(XmlConfigBuilder.java:213)
Caused by: java.io.IOException: Stream closed
        at [email protected]/java.io.BufferedInputStream.getInIfOpen(BufferedInputStream.java:157)
11月 21, 2022 7:41:36 下午 com.hazelcast.config.XmlConfigBuilder
严重: Failed to parse the inputstream
Exception: Stream closed
11月 21, 2022 7:41:36 下午 io.vertx.core.impl.VertxImpl
严重: Failed to initialize clustered Vert.x
com.hazelcast.config.InvalidConfigurationException: Stream closed
        at com.hazelcast.config.XmlConfigBuilder.parse(XmlConfigBuilder.java:213)
Caused by: java.io.IOException: Stream closed
        at [email protected]/java.io.BufferedInputStream.getInIfOpen(BufferedInputStream.java:157)
11月 21, 2022 7:41:36 下午 io.vertx.core.impl.VertxImpl
严重: Failed to leave cluster
java.lang.NullPointerException
        at io.vertx.spi.cluster.hazelcast.HazelcastClusterManager.lambda$leave$5(HazelcastClusterManager.java:243)
com.hazelcast.config.InvalidConfigurationException: Stream closed
        at com.hazelcast.config.XmlConfigBuilder.parse(XmlConfigBuilder.java:213)
Caused by: java.io.IOException: Stream closed
        at [email protected]/java.io.BufferedInputStream.getInIfOpen(BufferedInputStream.java:157)
com.hazelcast.config.InvalidConfigurationException: Stream closed
        at com.hazelcast.config.XmlConfigBuilder.parse(XmlConfigBuilder.java:213)
Caused by: java.io.IOException: Stream closed
        at [email protected]/java.io.BufferedInputStream.getInIfOpen(BufferedInputStream.java:157)

@linghengqian
Copy link
Contributor Author

  • I think I solved the problem above.
  • image

@linghengqian
Copy link
Contributor Author

  • I noticed that vertx-core doesn't seem to need GraalVM reachability metadata to run nativeTest properly. From this point of view, I don't see the need to add support for vertx-core . Unless a friend gives an example of a failed nativeTest.

@linghengqian linghengqian closed this as not planned Won't fix, can't repro, duplicate, stale Jan 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant