查看CSE源码，发现在bizkeeper包下已定义了告警事件：CircutBreakerEvent，请教下，业务侧如何使用该组件，告警日志会打印到哪里

{"thread":"vert.x-eventloop-thread-1","level":"ERROR","loggerName":"org.apache.servicecomb.transport.rest.vertx.RestServerVerticle","message":"","thrown":{"commonElementCount":0,"localizedMessage":"io.vertx.core.VertxException: Key/certificate is mandatory for SSL","message":"io.vertx.core.VertxException: Key/certificate is mandatory for SSL","name":"io.vertx.core.VertxException","cause":{"commonElementCount":16,"localizedMessage":"Key/certificate is mandatory for SSL","message":"Key/certificate is mandatory for SSL","name":"io.vertx.core.VertxException","extendedStackTrace":[{"class":"io.vertx.core.net.impl.SSLHelper","method":"createContext","file":"SSLHelper.java","line":259,"exact":false,"location":"vertx-core-3.6.3.jar!/","version":"3.6.3"}]},"extendedStackTrace":[{"class":"io.vertx.core.net.impl.SSLHelper","method":"createContext","file":"SSLHelper.java","line":299,"exact":false,"location":"vertx-core-3.6.3.jar!/","version":"3.6.3"},{"class":"io.vertx.core.net.impl.SSLHelper","method":"getContext","file":"SSLHelper.java","line":474,"exact":false,"location":"vertx-core-3.6.3.jar!/","version":"3.6.3"},{"class":"io.vertx.core.net.impl.SSLHelper","method":"validate","file":"SSLHelper.java","line":499,"exact":false,"location":"vertx-core-3.6.3.jar!/","version":"3.6.3"},{"class":"io.vertx.core.http.impl.HttpServerImpl","method":"listen","file":"HttpServerImpl.java","line":220,"exact":false,"location":"vertx-core-3.6.3.jar!/","version":"3.6.3"},{"class":"io.vertx.core.http.impl.HttpServerImpl","method":"listen","file":"HttpServerImpl.java","line":191,"exact":false,"location":"vertx-core-3.6.3.jar!/","version":"3.6.3"},{"class":"org.apache.servicecomb.transport.rest.vertx.RestServerVerticle","method":"startListen","file":"RestServerVerticle.java","line":216,"exact":false,"location":"transport-rest-vertx-1.2.0.B011.jar!/","version":"1.2.0.B011"},{"class":"org.apache.servicecomb.transport.rest.vertx.RestServerVerticle","method":"start","file":"RestServerVerticle.java","line":115,"exact":false,"location":"transport-rest-vertx-1.2.0.B011.jar!/","version":"1.2.0.B011"},{"class":"io.vertx.core.impl.DeploymentManager","method":"lambda$doDeploy$8","file":"DeploymentManager.java","line":494,"exact":false,"location":"vertx-core-3.6.3.jar!/","version":"3.6.3"},{"class":"io.vertx.core.impl.ContextImpl","method":"executeTask","file":"ContextImpl.java","line":320,"exact":false,"location":"vertx-core-3.6.3.jar!/","version":"3.6.3"},{"class":"io.vertx.core.impl.EventLoopContext","method":"lambda$executeAsync$0","file":"EventLoopContext.java","line":38,"exact":false,"location":"vertx-core-3.6.3.jar!/","version":"3.6.3"},{"class":"io.netty.util.concurrent.AbstractEventExecutor","method":"safeExecute","file":"AbstractEventExecutor.java","line":163,"exact":true,"location":"netty-common-4.1.36.Final.jar!/","version":"4.1.36.Final"},{"class":"io.netty.util.concurrent.SingleThreadEventExecutor","method":"runAllTasks","file":"SingleThreadEventExecutor.java","line":405,"exact":true,"location":"netty-common-4.1.36.Final.jar!/","version":"4.1.36.Final"},{"class":"io.netty.channel.nio.NioEventLoop","method":"run","file":"NioEventLoop.java","line":500,"exact":true,"location":"netty-transport-4.1.36.Final.jar!/","version":"4.1.36.Final"},{"class":"io.netty.util.concurrent.SingleThreadEventExecutor$5","method":"run","file":"SingleThreadEventExecutor.java","line":906,"exact":true,"location":"netty-common-4.1.36.Final.jar!/","version":"4.1.36.Final"},{"class":"io.netty.util.internal.ThreadExecutorMap$2","method":"run","file":"ThreadExecutorMap.java","line":74,"exact":true,"location":"netty-common-4.1.36.Final.jar!/","version":"4.1.36.Final"},{"class":"io.netty.util.concurrent.FastThreadLocalRunnable","method":"run","file":"FastThreadLocalRunnable.java","line":30,"exact":true,"location":"netty-common-4.1.36.Final.jar!/","version":"4.1.36.Final"},{"class":"java.lang.Thread","method":"run","file":"Thread.java","line":748,"exact":true,"location":"?","version":"1.8.0_222"}]},"endOfBatch":false,"loggerFqcn":"org.apache.logging.slf4j.Log4jLogger","instant":{"epochSecond":1577244158,"nanoOfSecond":914000000},"threadId":52,"threadPriority":5,"module":"rtcamservice","@timestamp":"2019-12-25T03:22:38.914+0000","endpoint":"*"}

上传文件的接口    @PostMapping("/importAll")    @Consumes(MediaType.MULTIPART_FORM_DATA_VALUE)    public ImportDetail importAll(@RequestPart(name = "file") MultipartFile file) {        return excelService.fullImportKnowledge(file);    }初始异常和这个一样：https://bbs.huaweicloud.com/forum/thread-13857-1-1.html设置较长idleTimeoutInSeconds的时间后，异常日志没有了，但是问题还是一样，报500错误，查看slb日志，发现没有转发日志。nginx配置已上传附件。

ERROR org.apache.servicecomb.transport.rest.vertx.RestServerVerticle -Unexpected error in server.cause:SSLException,message:handshake timed out3s钟出现一次这个error

我们产品的服务，注册到微服务引擎CSE上，通过HTTPS，我们服务想开启单向认证，怎么获取CSE的证书？CSE是否像数据库一样，给连接的服务提供CA证书？

CSE开启sslEnabled=true配置后，那对外的端口就支持https请求，并且证书用的是自己在ssl.trustStore的证书。原先配置的心跳健康检查失败，即使配置成https也会失败，那应该怎么添加心跳检查？

开启TLS后，是否支持配置重协商，请问怎么操作

您好，使用CSE Mesher的方式进行微服务的部署，纯http方式没有问题，现在需要引入https：开始的时候服务调用链是A->B，然后我给A配置了mesher.Consumer，B配置了mesher.Provider，互相之间可以正常访问。现在的调用链是 A->B->C ，我给A配置了mesher.Consumer，B同时配置了mesher.Provider和mesher.Consumer，然后C配置了mesher.Provider，结果现在发现A->B是正常的，但是B->C就存在问题，想问下如果一个微服务又做被访问方，又做访问方，这个配置需要如何配呢？是能支持还是不能支持呢？盼复，感谢！

cse集成springboot，发现cse的端口号8080和springboot的端口号8010都可以访问。因为cse开启了sslEnable，希望通过ssl访问cse。想关闭springboot的端口号。请问，如何关闭springboot的端口号application.properties:    server.port=8010    server.address=0.0.0.0microservice.yaml:cse:  service:    registry:      address: https://xx.xx.xx.xx:xx  rest:    address: 0.0.0.0:8080?sslEnabled=true

想用CSE Handler实现访问控制。基本思路是调用IAM的校验token接口，故需要传入IAM endpoint配置参数。配置中心使用Apollo，请问Handler支持Spring 的依赖注入吗？或者有什么办法可以在Handler中获取到Apollo的配置？

cse-dependency 2.3.73版本的cse ，对应的springboot1 是1.5.14版本，对应的springboot2是2.0.4版本，不清楚为什么cse会引入1.5.12版本

基于CSE开发微服务，集成方式参考：在Spring Boot中使用CSE https://support.huaweicloud.com/devg-servicestage/cse_java_0037.html请问： 集成CSE后必须使用CSE的方式（@RestSchema）开发REST接口吗？ @RestController和@RestSchema的区别是什么？集成CSE后使用@RestController是不是会导致无法使用CSE内置的负载均衡、服务治理和调用链跟踪（APM埋点）等功能？（https://bbs.huaweicloud.com/blogs/115961）

最近项目要从tomcat迁移到女娲部署。由于业务需要，需要获取其他业务设置的cookie，cookie的值中包含特殊字符， 在cse中通过HttpServletRequestEx.getCookies()获取不到这个cookie在tomcat中，我们是在 tomcat/conf/context.xml文件中配置<CookieProcessor className ="org.apache.tomcat.util.http.LegacyCookieProcessor"/>解决这个问题的，如下图请问使用cse需要怎么配置？

2.3.39版本的CSE在不配置注册中心地址的时候，是可以直接通过指定ip的方式直接调用在升级到2.3.70之后，不配置注册中心地址的时候，指定ip调用会报503 Service Unavailable，服务端返回：不配置注册中心地址指直接删除下面的配置service:    registry:      address: http://10.10.10.10:30100请问是否有方法规避这个问题？能够在不配置注册中心的情况下使用