0

After upgrade from 2.7.2 to 2.7.3 or 2.7.4 my quarkus project doesn't start anymore. I get following Exception:

Caused by: java.lang.NoSuchFieldError: ACCESS_CONTROL_ALLOW_PRIVATE_NETWORK
at io.vertx.core.http.HttpHeaders.<clinit>(HttpHeaders.java:106)
at io.vertx.core.http.impl.headers.HeadersMultiMap.<clinit>(HeadersMultiMap.java:63)
at io.quarkus.smallrye.openapi.runtime.OpenApiHandler.<clinit>(OpenApiHandler.java:24)
at io.quarkus.smallrye.openapi.runtime.OpenApiRecorder.handler(OpenApiRecorder.java:35)

Maybe it is releated to the upgrade of open api https://github.com/quarkusio/quarkus/pull/23886

When I disable open api it starts

quarkus.smallrye-openapi.enable=false
Felix Backmann
  • 33
  • 3

3 Answers3

0

Your problem seems to be related to this one, So i believe we have 2 workarounds:

First try using different browser than chrome (if you don't, go directly to second step)

Then, try enabling CORS in your application.properties like following :

quarkus.http.cors=true
Jacouille
  • 951
  • 8
  • 14
0

My problem was caused by a dependency with an older version of netty.

Updating netty fixed the problem.

Felix Backmann
  • 33
  • 3
0

https://stackoverflow.com/a/71423882/9651670

Thanks, this answer helped me a lot. I had to force a specific netty version on a previous update for azure/microsoft libs to work. Now they work with default managed version from quarkus and i removed netty-bom from dependencymanagement instead of updating it.

bumbel
  • 1
  • 1
  • As it’s currently written, your answer is unclear. Please [edit] to add additional details that will help others understand how this addresses the question asked. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – MD. RAKIB HASAN Mar 16 '22 at 12:16
  • Difference was updating the dependency and propably run in the problem again vs. removing the own handling of version for netty and let quarkus handle the version and maybe be safe forever :) – bumbel Mar 17 '22 at 13:22