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...
Bumps [jmockit](https://github.com/jmockit/jmockit1) from 1.30 to 1.49. Commits See full diff in compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
``` 2022-07-28 14:36:45.020|[]|mock-thread|WARN |SCBEngine.java:513|The request is rejected. Cannot process the request due to STATUS = STARTING 2022-07-28 14:36:45.020|[]|mock-thread|WARN |VehicleTaskEndListener.java:64|clear busyTag of [335157342402481152] failed 2022-07-28 14:36:45.215|[]|mock-thread|INFO |MicroserviceVersions.java:93|create MicroserviceVersions, appId=mockAppId, microserviceName=mockMicro. 2022-07-28...
I have an issue in `CommonHttpDispatcher` in that the consumer auth handlers configured for the registered third party microservice are not triggered. Can you help here? Why handlers are not...
https://stackoverflow.com/questions/3481664/semicolon-as-url-query-separator The W3C Recommendation from 1999 is obsolete. The current status, according to the 2014 W3C Recommendation, is that semicolon is now illegal as a parameter separator: 规范上说"；"不作为 分割符，请帮忙看看这个地方 CSE是否能将分割符做成可配置；这样既能支持老产品兼容，也能满足新规范要求
- 背景：服务收到大量请求；cse注册地址填写错误； - 定位过程： io.vertx.core.http.impl.pool.Pool 里面**waitersQueue**发生内存泄漏，分析pom文件该jar包由cse依赖引入，debug代码发现位于org.apache.servicecomb.serviceregistry.client.http.retry方法中调用，并且由于地址错误产生了大量日志 求助： 帮解答一下retry方法调用场景，以及内存泄漏问题
现在主要是在一种动态扩容场景，比如A调用B，现在需要增加一个B服务的实例B1，由于B1启动时，需要拉取很多配置信息，需要耗费一定的时长，若这个时候A来调用B1，则会出现请求调用失败，想看看ServiceComb有没有机制来避免这种问题，比如B1启动完成时，再通知服务中心A可以调用B1了。
EdgeInvocation. edgeInvoke()中会找到最新版本的微服务实例信息，然后根据最新版本的微服务实例信息转发请求，在查找最新版本的微服务实例信息时，需要过滤出状态为上线的微服务实例，这样是否更合理？
Today Zipkin trace logs 2 custom tags namely `http.method` & `http.path`. Is there a way to add more custom tags like `instanceId`. Also `Server` trace displays only the IPAddress and...