zhangaijing commented on issue #3516:
URL:
https://github.com/apache/servicecomb-java-chassis/issues/3516#issuecomment-1345755164
我们现在有个项目是要基于原来的一个项目上做开发的,现在测试下来使用原来的微服务名是能够在注册中心注册上去的.但换另一个微服务名就不行.....备注:
两个配置一模一样.
我们现在先用原来的微服务名注册中心是有服务了,但出现微服务之间无法调用: 报错信息如下:
2022-12-12 09:48:44:044 [vert.x-eventloop-thread-7] [INFO ]
com.hoolink.manage.gateway.dispatcher.ApiDispatcher >> [txId]:
3A10053E13E54C338A69444D1A611382 microservice is: manage-crm-rpc, method is:
/web/seeyon/getTest, params is:
2022-12-12 09:48:44:044 [pool-2-thread-5] [ERROR]
org.apache.servicecomb.common.rest.AbstractRestInvocation >> unknown rest
exception.
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.servicecomb.swagger.invocation.exception.ExceptionFactory
at
org.apache.servicecomb.swagger.invocation.Response.createConsumerFail(Response.java:129)
at
org.apache.servicecomb.core.provider.consumer.InvokerUtils.reactiveInvoke(InvokerUtils.java:117)
at
org.apache.servicecomb.provider.pojo.Invoker.completableFutureInvoke(Invoker.java:185)
at org.apache.servicecomb.provider.pojo.Invoker.invoke(Invoker.java:158)
at com.sun.proxy.$Proxy111.getSessionUser(Unknown Source)
at
com.hoolink.manage.gateway.handler.AuthHandler.handle(AuthHandler.java:74)
at org.apache.servicecomb.core.Invocation.next(Invocation.java:204)
at
org.apache.servicecomb.common.rest.AbstractRestInvocation.doInvoke(AbstractRestInvocation.java:243)
at
org.apache.servicecomb.common.rest.AbstractRestInvocation.invoke(AbstractRestInvocation.java:217)
at
org.apache.servicecomb.common.rest.AbstractRestInvocation.runOnExecutor(AbstractRestInvocation.java:201)
at
org.apache.servicecomb.common.rest.AbstractRestInvocation.lambda$scheduleInvocation$0(AbstractRestInvocation.java:160)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
2022-12-12 09:48:44:044 [pool-2-thread-5] [ERROR]
org.apache.servicecomb.common.rest.AbstractRestInvocation >> rest server
onRequest error
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.servicecomb.swagger.invocation.exception.ExceptionFactory
at
org.apache.servicecomb.swagger.invocation.Response.createProducerFail(Response.java:134)
at
org.apache.servicecomb.common.rest.AbstractRestInvocation.sendFailResponse(AbstractRestInvocation.java:251)
at
org.apache.servicecomb.common.rest.AbstractRestInvocation.invoke(AbstractRestInvocation.java:220)
at
org.apache.servicecomb.common.rest.AbstractRestInvocation.runOnExecutor(AbstractRestInvocation.java:201)
at
org.apache.servicecomb.common.rest.AbstractRestInvocation.lambda$scheduleInvocation$0(AbstractRestInvocation.java:160)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
Exception in thread "pool-2-thread-5" java.lang.NoClassDefFoundError: Could
not initialize class
org.apache.servicecomb.swagger.invocation.exception.ExceptionFactory
at
org.apache.servicecomb.swagger.invocation.Response.createProducerFail(Response.java:134)
at
org.apache.servicecomb.common.rest.AbstractRestInvocation.sendFailResponse(AbstractRestInvocation.java:251)
at
org.apache.servicecomb.common.rest.AbstractRestInvocation.lambda$scheduleInvocation$0(AbstractRestInvocation.java:163)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:750)
2022-12-12 09:49:06:006 [pool-1-thread-1] [WARN ]
com.hoolink.sdk.cloud.CloudConfigurationSourceImpl >> Config value cache
changed: action:SET; item:[service_description.version]
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
