apache / apache/servicecomb-java-chassis
Service registration is failing with : Could not initialize class io.vertx.core.http.HttpHeaders
- Langage dominant
- Java
- Étoiles
- 1.9k
- Forks
- 814
- Merge moyen
- 8 j 23 h
- PR mergées (30 j)
- 1
Description
Hello,
MY gateway service registration if failing with
```
java.lang.NoClassDefFoundError: Could not initialize class io.vertx.core.http.HttpHeaders
java.lang.NoSuchFieldError: ACCESS_CONTROL_ALLOW_PRIVATE_NETWORK
```
Below are the error logs in startup. This error starts to occur recently. Not sure if it is related to any library conflicts.
`2022-08-22 10:17:43.104 ERROR 18821 --- [ntloop-thread-1] o.a.s.s.client.http.RestClientUtil : GET /v4/default/registry/existence?appId=talech-services&type=microservice&serviceName=gateway&env&version=1.0.1 fail, endpoint is 127.0.0.1:30100, message: Could not initialize class io.vertx.core.http.HttpHeaders
2022-08-22 10:17:43.105 WARN 18821 --- [ntloop-thread-1] o.a.s.s.c.h.ServiceRegistryClientImpl : invoke service [127.0.0.1:30100] failed, retry address [127.0.0.1:30100].
2022-08-22 10:17:43.106 ERROR 18821 --- [ntloop-thread-1] o.a.s.s.client.http.RestClientUtil : GET /v4/default/registry/existence?appId=talech-services&type=microservice&serviceName=gateway&env&version=1.0.1 fail, endpoint is 127.0.0.1:30100, message: Could not initialize class io.vertx.core.http.HttpHeaders
2022-08-22 10:17:43.106 WARN 18821 --- [ntloop-thread-1] o.a.s.s.c.h.ServiceRegistryClientImpl : invoke service [127.0.0.1:30100] failed, retry address [127.0.0.1:30100].
2022-08-22 10:17:43.106 ERROR 18821 --- [ntloop-thread-1] o.a.s.s.client.http.RestClientUtil : GET /v4/default/registry/existence?appId=talech-services&type=microservice&serviceName=gateway&env&version=1.0.1 fail, endpoint is 127.0.0.1:30100, message: Could not initialize class io.vertx.core.http.HttpHeaders
2022-08-22 10:17:43.107 INFO 18821 --- [Center Task [0]] o.a.s.s.adapter.EnvAdapterManager : Start process microservice with adapter default-env-adapter
`
Appreciate help from any one.
Thanks
Meenakshi
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Aucun fichier source ni test n’est indiqué. Commencez par reproduire l’enregistrement du service gateway et retracer l’échec signalé lors de l’initialisation de HttpHeaders ainsi que le soupçon de conflit de dépendances ; le travail est terminé lorsque l’enregistrement réussit sans NoClassDefFoundError ni NoSuchFieldError.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java
- Domaine
- backend
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100