This is an automated email from the ASF dual-hosted git repository.
tianxiaoliang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-service-center.git
The following commit(s) were added to refs/heads/master by this push:
new d0a2bec Upgrade
FoxCATT opened a new issue #1619: cse是否支持schemaId或mappath粒度的契约注册控制
URL: https://github.com/apache/servicecomb-java-chassis/issues/1619
## 问题场景
同一个微服务区分功能部署在两个集群，契约相同且注册到同一注册中心。但由于两个集群中环境不同，部分接口只能在其中一个集群中提供正确的服务，但注册中心有两个集群全部实例的信息，导致其他微服务在调用这个微服务的接口时会得不到正确的结果。
## 问题
zhangbeiyuan-hw opened a new issue #1620: edge配置是如何设置默认配置的？可以根据服务名自动转发服务
URL: https://github.com/apache/servicecomb-java-chassis/issues/1620
后台我有好几个服务，不想每个都配置map映射，想通过default配置实现自动转发，如下配置：
如果我有两个微服务，microserviceName是serverA，提供的url是 /v1/users
另一个微服务microserviceName是serverB，提供url是
zhangbeiyuan-hw opened a new issue #1614: 启动TLS后，前台通过cse调用后台接口，返回490错误
URL: https://github.com/apache/servicecomb-java-chassis/issues/1614
前后调用后台，启动tls后，cse调用报 490错误
response： {"message":"Cse Internal Bad Request"}
求助该如何定位解决，配置文件如下
前台配置：
```yaml
# all interconnected
heyile opened a new pull request #1615: [SCB-1794] remove commons-beautils from
SDK, as the version 1.9.3 is …
URL: https://github.com/apache/servicecomb-java-chassis/pull/1615
…not trusted
Follow this checklist to help us incorporate your contribution quickly and
easily:
-
Bluselye opened a new issue #1616: ServiceComb
进行RPC调用时RestClientInvocation可以支持自已实现么？
URL: https://github.com/apache/servicecomb-java-chassis/issues/1616
ServiceComb 进行RPC调用时会通过RestClientInvocation进行转发，这个类支持自定义扩展么？如果可以该如何配置？
heyile opened a new pull request #1617: [SCB-1793] use @RequestHeader(value
="xxx") and aggregatedParam at sa…
URL: https://github.com/apache/servicecomb-java-chassis/pull/1617
…me time, it will throw null pointer exception
Follow this checklist to help us incorporate your
heyile commented on issue #1614: 启动TLS后，前台通过cse调用后台接口，返回490错误
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1614#issuecomment-594251538
SDK 的版本提供下. 还有 你只把配置贴上来, 很多细节都不知道. 可以给一个链接, 连接到自己的github demo 仓库吗.
例如
```
ssl.sslCustomClass:
h00379108 commented on issue #1607: java的服务（集成java cse的sdk)调用go的服务（集成go cse
sdk）通信报错
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1607#issuecomment-594257723
版本不限
This is an automated message from the
zhangbeiyuan-hw commented on issue #1614: 启动TLS后，前台通过cse调用后台接口，返回490错误
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1614#issuecomment-594282699
请教一下，下面这个配置是不是做路由的，应该如何配置，有没有指导？
```yaml
http:
dispatcher:
edge:
default:
humingcheng opened a new pull request #639: Upgrade etcd to v3.3.8,
improvement: https://github.com/etcd-io/etcd/pull/9840
URL: https://github.com/apache/servicecomb-service-center/pull/639
Fix high CPU usage when disconnected from etcd server
Follow this checklist to help us
heyile commented on issue #1614: 启动TLS后，前台通过cse调用后台接口，返回490错误
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1614#issuecomment-594298507
可以参考下这个文档. 类似问题可以尝试自助在文档里面搜索
http://1v96us.coding-pages.com/docs/java-chassis/zh_CN/edge/by-servicecomb-sdk/
coveralls commented on issue #1617: [SCB-1793] use @RequestHeader(value ="xxx")
and aggregatedParam at sa…
URL:
https://github.com/apache/servicecomb-java-chassis/pull/1617#issuecomment-594308379
[![Coverage
coveralls commented on issue #1618: [SCB-1794] remove commons-beautils from
SDK, as the version 1.9.3 is …
URL:
https://github.com/apache/servicecomb-java-chassis/pull/1618#issuecomment-594313204
[![Coverage
WillemJiang commented on issue #635: 关于SAGA模式设计上的问题
URL:
https://github.com/apache/servicecomb-pack/issues/635#issuecomment-594242193
EventScanner 的解决办法是有一定局限性的，
WindyDovs commented on issue #635: 关于SAGA模式设计上的问题
URL:
https://github.com/apache/servicecomb-pack/issues/635#issuecomment-594296048
> EventScanner 的解决办法是有一定局限性的，
zhangbeiyuan-hw commented on issue #1614: 启动TLS后，前台通过cse调用后台接口，返回490错误
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1614#issuecomment-594309560
删除证书重新添加后，又报490错了，帮忙看一下，在我的私有库上
https://github.com/zhangbeiyuan-hw/test-project
zhangbeiyuan-hw commented on issue #1614: 启动TLS后，前台通过cse调用后台接口，返回490错误
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1614#issuecomment-594249256
### 补充调用接口
Request URL: https://openmep.org:8081/user-mgmt-be/v1/users/auth
Request Method: POST
Status Code: 490
heyile commented on issue #1613:
将多个query参数聚合为一个POJO类，同时使用POJO和@RequestHeader会导致NullPointerException异常
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1613#issuecomment-594252250
确实有问题. 问题我复现了 提了 issue
https://issues.apache.org/jira/projects/SCB/issues/SCB-1793
heyile commented on issue #1613:
将多个query参数聚合为一个POJO类，同时使用POJO和@RequestHeader会导致NullPointerException异常
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1613#issuecomment-594268443
你可以使用 如下进行规避
```
@RequestMapping(value = "/events2/{project_id}", method =
heyile commented on issue #1613:
将多个query参数聚合为一个POJO类，同时使用POJO和@RequestHeader会导致NullPointerException异常
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1613#issuecomment-594268800
当前对value 的实现有问题. 是按照name 实现的
zhangbeiyuan-hw commented on issue #1614: 启动TLS后，前台通过cse调用后台接口，返回490错误
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1614#issuecomment-594282283
早上重启服务又好了，没有昨晚那个异常了。现在可以访问
This is an automated message
coveralls commented on issue #639: Upgrade etcd to v3.3.8, improvement:
https://github.com/etcd-io/etcd/pull/9840
URL:
https://github.com/apache/servicecomb-service-center/pull/639#issuecomment-594305119
[![Coverage
heyile opened a new pull request #1618: [SCB-1794] remove commons-beautils from
SDK, as the version 1.9.3 is …
URL: https://github.com/apache/servicecomb-java-chassis/pull/1618
…not trusted
Follow this checklist to help us incorporate your contribution quickly and
easily:
-
heyile closed pull request #1615: [SCB-1794] remove commons-beautils from SDK,
as the version 1.9.3 is …
URL: https://github.com/apache/servicecomb-java-chassis/pull/1615
This is an automated message from the Apache Git
zhfeng commented on issue #635: 关于SAGA模式设计上的问题
URL:
https://github.com/apache/servicecomb-pack/issues/635#issuecomment-594318155
状态机模型是在Alpha server端来使用的，目的也是为了协调Saga
heyile commented on issue #1619: cse是否支持schemaId或mappath粒度的契约注册控制
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1619#issuecomment-594355736
@liubao68 .
This is an automated message from the Apache Git
Bluselye commented on issue #1610:
ServiceComb在RPC调用时如果业务请求报错了怎么样才能拿到请求报错的InvocationContext ？
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1610#issuecomment-594355434
heyile removed a comment on issue #1602: 请教，highway通信模式下是否可以指定ip访问特定实例的接口
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1602#issuecomment-593797064
SpringMVC JAX-RS RPC 这些只是服务端编程模型，说白了只是你写代码的形式.
highway 这些是传输模型. 两个模型本来就是解耦的.
我给你的示例 是 SpringMVC 编程模型. 至于用不用 highway
WindyDovs commented on issue #635: 关于SAGA模式设计上的问题
URL:
https://github.com/apache/servicecomb-pack/issues/635#issuecomment-594338406
> 状态机模型是在Alpha server端来使用的，目的也是为了协调Saga
WindyDovs closed issue #635: 关于SAGA模式设计上的问题
URL: https://github.com/apache/servicecomb-pack/issues/635
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
heyile commented on issue #1610:
ServiceComb在RPC调用时如果业务请求报错了怎么样才能拿到请求报错的InvocationContext ？
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1610#issuecomment-594349535
能介绍一下你的业务场景吗? 为啥要 Client 的 InvocationContext
tianxiaoliang merged pull request #639: Upgrade etcd to v3.3.8, improvement:
https://github.com/etcd-io/etcd/pull/9840
URL: https://github.com/apache/servicecomb-service-center/pull/639
This is an automated message from the
YYKI commented on issue #1602: 请教，highway通信模式下是否可以指定ip访问特定实例的接口
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1602#issuecomment-594353316
提issue前，网上有的资料基本是都看了下的，有些地方确实不太理解，经过本地测试，再确认一个问题
1、只提供rest通信
```
microservice.yaml
rest:
address: 0.0.0.0:8080 #
Caixinyang opened a new issue #1613:
将多个query参数聚合为一个POJO类，同时使用POJO和@RequestHeader会导致NullPointerException异常
URL: https://github.com/apache/servicecomb-java-chassis/issues/1613
Caused by: java.lang.NullPointerException: null
at
heyile commented on issue #1613:
将多个query参数聚合为一个POJO类，同时使用POJO和@RequestHeader会导致NullPointerException异常
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1613#issuecomment-593860998
最好给下demo. 至少给下 SDK 版本信息
This
heyile commented on issue #1611:
ServiceComb有access.log访问自身的日志，那有没有调用其他服务的outcall.log?如果有该怎么配置？
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1611#issuecomment-593863540
暂时没这个能力. 如果可以. 你可以给个 PR, 把能力补充一下.
Caixinyang commented on issue #1613:
将多个query参数聚合为一个POJO类，同时使用POJO和@RequestHeader会导致NullPointerException异常
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1613#issuecomment-593867522
com.huawei.paas.cse
cse-solution-service-engine
heyile commented on issue #1610:
ServiceComb在RPC调用时如果业务请求报错了怎么样才能拿到请求报错的InvocationContext ？
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1610#issuecomment-593870439
可以.
```java
public String sayHi(String name) {
InvocationContext context =
Bluselye commented on issue #1610:
ServiceComb在RPC调用时如果业务请求报错了怎么样才能拿到请求报错的InvocationContext ？
URL:
https://github.com/apache/servicecomb-java-chassis/issues/1610#issuecomment-593871950
这个试了下，获取到的是Service的不是作为Client的InvocationContext
try{
rpc.method
}catch(Exception e){
Bluselye opened a new issue #1610:
ServiceComb在RPC调用时如果业务请求报错了怎么样才能拿到请求报错的InvocationContext ？
URL: https://github.com/apache/servicecomb-java-chassis/issues/1610
在RPC调用时发生了请求异常，此时异常在try-catch中捕获，
如果在当前想要拿到此次RPC请求的异常的InvocationContext ，该怎么取？有办法取吗？
zhangbeiyuan-hw opened a new issue #1612: bmi/webapp
这里sample如何启动，webroot是不是需要配置static的绝对路径？
URL: https://github.com/apache/servicecomb-java-chassis/issues/1612
配置如下，这里是否要配置绝对路径，能否按照相对路径配置到resuource/static下？windows系统下怎么配置？
# This is web root for windows server, change this path
Bluselye opened a new issue #1611:
ServiceComb有access.log访问自身的日志，那有没有调用其他服务的outcall.log?如果有该怎么配置？
URL: https://github.com/apache/servicecomb-java-chassis/issues/1611
ServiceComb有access.log访问自身的日志，那有没有调用其他服务的outcall.log?如果有该怎么配置？
43 matches
Mail list logo
