servicecomb-java-chassis
servicecomb-java-chassis copied to clipboard
apache
ServiceComb Java Chassis is a Software Development Kit (SDK) for rapid development of microservices in Java, providing service registration, service discovery, dynamic routing, and service management...
做性能测试不断有这个报错，不知道什么原因， 2022-07-15 00:00:02.952|transport-vert.x-eventloop-thread-0|DEBUG|RestServerVerticle.java:lambda$start$2:114||Unexpected error in server.cause:ClosedChannelException,message:null 2022-07-15 00:00:03.262|transport-vert.x-eventloop-thread-1|DEBUG|RestServerVerticle.java:lambda$start$2:114||Unexpected error in server.cause:ClosedChannelException,message:null 2022-07-15 00:00:12.193|transport-vert.x-eventloop-thread-0|DEBUG|RestServerVerticle.java:lambda$start$2:114||Unexpected error in server.cause:ClosedChannelException,message:null 看社区有个类似的问题，是否解决了？ https://github.com/apache/servicecomb-java-chassis/issues/2050
Java-Chassis的限流模块在动态配置场景下存在问题 ## 问题触发场景 假设存在两个Java-Chassis框架开发的微服务 A 和 B, B微服务有一个契约接口, 其`qualifiedName`=`B.schema.oper`. 如果业务在B启动后, 先在配置中心为 B 微服务添加一条对`ANY.schema.oper`接口的限流规则, 再触发 A 调用 B 的 `oper` 接口, 则 B 的 `org.apache.servicecomb.qps.QpsControllerManager#configQpsControllerMap` 属性中缓存的 `A.schema.oper` 的`QpsStrategy`对象实际是 `ANY.schema.oper` 配置项的. 而当用户再从配置中心删除`ANY.schema.oper`接口的限流规则时,...
2020-11-12 10:29:07,247:ERROR vert.x-eventloop-thread-13 (TcpServer.java:82) - Unexpected error in server.cause:ClosedChannelException,message:null 改了空闲超时之类的没用。
After registering third party service in the service center with its own name (say BusinessThirdParty) and schema, is it possible to route to this third party service dynamically with the...
https://github.com/apache/servicecomb-java-chassis/blob/703a972576b35154d9a9a46f087411fab86fd74a/transports/transport-rest/transport-rest-client/src/main/java/org/apache/servicecomb/transport/rest/client/http/RestClientInvocation.java#L123
java.lang.NumberFormatException: For input string: "2022-05-31T09:16:38.941Z" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:67) ~[?:?] at java.lang.Long.parseLong(Long.java:711) ~[?:?] at org.apache.servicecomb.foundation.protobuf.internal.schema.serializer.scalar.Int64WriteSchemas$Int64DynamicSchema.writeTo(Int64WriteSchemas.java:66) ~[foundation-protobuf-2.7.3.jar:2.7.3] at org.apache.servicecomb.foundation.protobuf.internal.schema.serializer.MessageWriteSchema.writeFromMap(MessageWriteSchema.java:192) ~[foundation-protobuf-2.7.3.jar:2.7.3] at org.apache.servicecomb.foundation.protobuf.internal.schema.serializer.MessageWriteSchema.writeTo(MessageWriteSchema.java:151) ~[foundation-protobuf-2.7.3.jar:2.7.3] at org.apache.servicecomb.foundation.protobuf.RootSerializer.serialize(RootSerializer.java:35) ~[foundation-protobuf-2.7.3.jar:2.7.3] at org.apache.servicecomb.codec.protobuf.definition.RequestRootSerializer.serialize(RequestRootSerializer.java:46) ~[common-protobuf-2.7.3.jar:2.7.3] at org.apache.servicecomb.transport.highway.HighwayOutputStream.write(HighwayOutputStream.java:32) ~[transport-highway-2.7.3.jar:2.7.3] at...
privateKeyFile: ./private.key # rsa key pairs publicKeyFile: ./public.key # rsa key pairs 这两个key 随便生成的吗？windows sevice center password怎么设置 客户端需要配置吗
serviceComb.rest.address仅支持0.0.0.0的方式来监听全网地址，无法配置为监听某些ip，是否会考虑增加监听某些ip的功能？
接口定义在单独的组件A中，已添加-parameters编译 服务 **B** 实现了该接口定义，部署注册成功，cse已正常显示生成的对应契约，参数名称也为定义好的名称 服务 **C** 在调用此接口时报错java.lang.IllegalStateException: parameter name is not present，但是另一个服务 **D** 在调用此接口时能够正常调用成功 是什么原因导致了这种情况~
### 问题描述 java chassis客户端访问服务器（以本地注册发现服务的方式），偶现490错误，报错Caused by: io.vertx.core.VertxException: Connection was closed 2022-06-20 08:04:40.081|[xxx]|transport-vert.x-eventloop-thread-0|ERROR|InvokerUtils.java:333|invoke failed, operation xxx, trace id xx org.apache.servicecomb.swagger.invocation.exception.InvocationException: InvocationException: code=490;msg=CommonExceptionData [message=Unexpected consumer error, please check logs for details] ### 定位过程...
