[GitHub] [servicecomb-docs] yangshaoqin1 opened a new pull request #88: [SCB-1162]document for PriorityProperty/InjectProperties/InjectProperty
yangshaoqin1 opened a new pull request #88: [SCB-1162]document for PriorityProperty/InjectProperties/InjectProperty URL: https://github.com/apache/servicecomb-docs/pull/88 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] wNee commented on issue #333: install issue
wNee commented on issue #333: install issue URL: https://github.com/apache/servicecomb-pack/issues/333#issuecomment-469550631 I have no problems. Thank you At 2019-03-05 09:15:16, "Willem Jiang" wrote: @wNee Did you still have some trouble to build the docker images of Alpha? I need to close this issue as there is no feedback for a long time, please let me know if you have any other question about it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] coveralls edited a comment on issue #419: [SCB-1182] Modify the default activation profile spring-boot-2 in the document
coveralls edited a comment on issue #419: [SCB-1182] Modify the default activation profile spring-boot-2 in the document URL: https://github.com/apache/servicecomb-pack/pull/419#issuecomment-469527238 [](https://coveralls.io/builds/21987217) Coverage remained the same at 90.245% when pulling **e5bee702a74ef1e10049ebf8a39e1d4396a04356 on coolbeevip:SCB-1182** into **0497507170282145fcd4a2a5290c6ca427f6d742 on apache:master**. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] coveralls edited a comment on issue #419: [SCB-1182] Modify the default activation profile spring-boot-2 in the document
coveralls edited a comment on issue #419: [SCB-1182] Modify the default activation profile spring-boot-2 in the document URL: https://github.com/apache/servicecomb-pack/pull/419#issuecomment-469527238 [](https://coveralls.io/builds/21987217) Coverage remained the same at 90.245% when pulling **e5bee702a74ef1e10049ebf8a39e1d4396a04356 on coolbeevip:SCB-1182** into **0497507170282145fcd4a2a5290c6ca427f6d742 on apache:master**. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-java-chassis] wujimin commented on issue #1112: JDK升级8U191之后，容器内线程数变少了，是否可以开放参数设置
wujimin commented on issue #1112: JDK升级8U191之后，容器内线程数变少了，是否可以开放参数设置 URL: https://github.com/apache/servicecomb-java-chassis/issues/1112#issuecomment-469534721 一般来说，eventloop逻辑，不需要去调整这个参数，cpu资源就那么多，再调整也没什么用 除非像样在eventloop中执行了不允许的：大循环/阻塞等待等等动作 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-java-chassis] wujimin edited a comment on issue #1112: JDK升级8U191之后，容器内线程数变少了，是否可以开放参数设置
wujimin edited a comment on issue #1112: JDK升级8U191之后，容器内线程数变少了，是否可以开放参数设置 URL: https://github.com/apache/servicecomb-java-chassis/issues/1112#issuecomment-469534721 一般来说，eventloop逻辑，不需要去调整这个参数，cpu资源就那么多，再调整也没什么用 除非在eventloop中执行了不允许的逻辑：大循环/阻塞等待等等动作 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[servicecomb-docs] branch master updated: Polish the documents of saga demo code
This is an automated email from the ASF dual-hosted git repository.
ningjiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-docs.git
The following commit(s) were added to refs/heads/master by this push:
new b57d2fb Polish the documents of saga demo code
b57d2fb is described below
commit b57d2fbd59382586d8d0759f569844a0bac19962
Author: Willem Jiang
AuthorDate: Tue Mar 5 12:06:03 2019 +0800
Polish the documents of saga demo code
---
saga-reference/zh_CN/SUMMARY.md | 3 ++-
saga-reference/zh_CN/{quickstart.md => saga-spring-demo-code.md} | 4 ++--
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/saga-reference/zh_CN/SUMMARY.md b/saga-reference/zh_CN/SUMMARY.md
index da33bcc..2b942c0 100644
--- a/saga-reference/zh_CN/SUMMARY.md
+++ b/saga-reference/zh_CN/SUMMARY.md
@@ -2,5 +2,6 @@
* [用户手册](user_guide_zh.md)
* [设计文档](design_zh.md)
* [TLS通信](enable_ssl.md)
+* [spring-saga-demo-代码解读](saga-spring-demo-code.md)
* [API](api/api.md)
-* [Q](faq/how_to_use_mysql_as_alpha_backend_database_zh.md)
\ No newline at end of file
+* [Q](faq/how_to_use_mysql_as_alpha_backend_database_zh.md)
diff --git a/saga-reference/zh_CN/quickstart.md
b/saga-reference/zh_CN/saga-spring-demo-code.md
similarity index 98%
rename from saga-reference/zh_CN/quickstart.md
rename to saga-reference/zh_CN/saga-spring-demo-code.md
index 2e645e2..5bb8ef6 100644
--- a/saga-reference/zh_CN/quickstart.md
+++ b/saga-reference/zh_CN/saga-spring-demo-code.md
@@ -1,4 +1,4 @@
-# Apache ServiceComb Pack ：Saga QuickStart
+# Apache ServiceComb Pack ：Saga Spring Demo 代码解读
###
[Saga-servicecomb-demo](https://github.com/apache/servicecomb-pack/tree/master/demo/saga-spring-demo)
背景介绍的ServiceComb Pack
@@ -49,5 +49,5 @@
1.用户发送Request请求调用业务方法(business logic)
2.preIntercept向alpha发送TxStartedEvent
3.被AOP拦截的方法(business logic)被调用
-4.当执行成功时postIntercept发送TxEndedEvent到alpha
+4.当执行成功时postIntercept发送TxEndedEvent到alpha
5.最后业务方法向用户发送response
[GitHub] [servicecomb-pack] coveralls commented on issue #419: [SCB-1182] Modify the default activation profile spring-boot-2 in the document
coveralls commented on issue #419: [SCB-1182] Modify the default activation profile spring-boot-2 in the document URL: https://github.com/apache/servicecomb-pack/pull/419#issuecomment-469527236 [](https://coveralls.io/builds/21985697) Coverage remained the same at 90.245% when pulling **00a2a10fb60a8075e528b8869e3d5bfe6b97a713 on coolbeevip:SCB-1182** into **0497507170282145fcd4a2a5290c6ca427f6d742 on apache:master**. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] coveralls commented on issue #419: [SCB-1182] Modify the default activation profile spring-boot-2 in the document
coveralls commented on issue #419: [SCB-1182] Modify the default activation profile spring-boot-2 in the document URL: https://github.com/apache/servicecomb-pack/pull/419#issuecomment-469527238 [](https://coveralls.io/builds/21985697) Coverage remained the same at 90.245% when pulling **00a2a10fb60a8075e528b8869e3d5bfe6b97a713 on coolbeevip:SCB-1182** into **0497507170282145fcd4a2a5290c6ca427f6d742 on apache:master**. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[servicecomb-docs] branch master updated: Clean up the quickstart.md
This is an automated email from the ASF dual-hosted git repository. ningjiang pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/servicecomb-docs.git The following commit(s) were added to refs/heads/master by this push: new 1a9e592 Clean up the quickstart.md 1a9e592 is described below commit 1a9e592c9de46199d2c2abbe49c4fbecec2cf9e7 Author: Willem Jiang AuthorDate: Tue Mar 5 11:52:25 2019 +0800 Clean up the quickstart.md --- saga-reference/zh_CN/quickstart.md | 40 ++ 1 file changed, 19 insertions(+), 21 deletions(-) diff --git a/saga-reference/zh_CN/quickstart.md b/saga-reference/zh_CN/quickstart.md index be8533b..2e645e2 100644 --- a/saga-reference/zh_CN/quickstart.md +++ b/saga-reference/zh_CN/quickstart.md @@ -1,55 +1,53 @@ # Apache ServiceComb Pack ：Saga QuickStart -### [Saga-servicecomb-demo](https://github.com/apache/servicecomb-pack) 背景介绍的Pack代码机制解读 +### [Saga-servicecomb-demo](https://github.com/apache/servicecomb-pack/tree/master/demo/saga-spring-demo) 背景介绍的ServiceComb Pack  -为了更好的学习Apache ServiceComb Pack，Demo设定一个实际需要分布式一致性的业务场景来方便理解。 -上图中：用户对预定服务Booking发起请求，其中租车订单服务car和酒店订单服务hotel没有依赖关系，可以并行处理，但对于我们的客户来说，只在所有预订成功后一次付费更加友好。 +为了更好的学习Apache ServiceComb Pack，saga-spring-demo设定一个实际需要分布式一致性的业务场景来方便理解。 +上图中：用户对预定服务Booking发起请求，其中租车订单服务car和酒店订单服务hotel没有依赖关系，租车服务是不知道酒店服务的执行情况。 对于预订服务来说，如果没有相关的服务调用协调机制的话，预订服务是很难保证其调用的租车服务以及酒店服务要么同时成功，要么同时失败。  -### Demo中的Saga场景 -上图中:Saga中包含两个组件，即Omega和Alpha, 另外还有用来持久化的DB。 -结合图一：三个服务，booking、car、hotel均为omega进程，均通过alpha协调。 +### Demo中的Saga实用场景 +上图中:Pack架构中包含两个重要组件，即Omega客户端和Alpha服务端, 另外还有用来持久化的DB。 +结合图一：Demo中有三个独立进程服务，订单服务booking、租车服务car、酒店服务hotel，这些服务进程中均包含了omega客户端，Omega客户端会向Alpha服务端发送服务调用的消息，这样alpha服务端充当协调器协调这些服务之间的调用。 -# Omega像一个agent内嵌各Service中,主要负责： +# Omega内嵌各Service进程中,主要负责： * 监控本地事务执行情况，并以Event形式向alpha上报事务执行状态。 * 异常情况下根据alpha下发的指令执行相应的补偿操作。 - -# Alpha充当协调者的角色，主要负责: + +# Alpha充当协调者的角色，主要负责: * 对本地事务的事件进行持久化存储。 * 在本地事务与全局事务出现不一致的情况下，Alpha会回调相关Omega进行补偿（最终保持全局事务一致）。 例：当异常情况下，如ServiceB的事务执行失败，Alpha扫描到Omega发送的TxAbortedEvent事件，就会回调ServiceA的补偿方法，执行自定义回滚逻辑，使各服务回到事务执行之前的状态。 -# 下面我们对Saga的事件建立初步了解后，再来看看Saga-servicecomb-demo具体直了写什么。 +# 现在我们具体看看saga-spring-demo涉及到的Saga事件。 ## Saga中的Event简介 [EventType事件参考代码](https://github.com/apache/servicecomb-pack/blob/master/pack-common/src/main/java/org/apache/servicecomb/pack/common/EventType.java) -SagaStartedEvent: 代表Saga事务的开始，Alpha接受到该事件会保存整个saga请求的上下文，其中包括多个事务/补偿请求 -TxStartedEvent: Alpha保存对应事务请求的上下文 -TXEndedEvent: Alpha保存对应事务请求及其回复 -TxAbortedEvent: Alpha保存对应事务请求和失败的原因 -TxCompensatedEvent: 保存对应补偿请求及其回复 -SagaEndedEvent: 标志着saga事务请求的结束，不需要保存任何内容 +* SagaStartedEvent: 代表Saga事务的开始，Alpha接受到该事件会保存整个saga事务的执行上下文，其中包括多个本地事务/补偿请求 +* TxStartedEvent: 本地事务开始事件，其中包含了本地事务执行的上下文（调用方法名，以及相关调用参数） +* TXEndedEvent: 本地事务结束事件 +* TxAbortedEvent: 本地事务执行失败事件，包含了事务执行失败的原因 +* TxCompensatedEvent: 本地事务补偿事件，Alpha会将本地事务执行的上下文传递给Omega，这样不需要Omega自己维护服务调用的状态。 +* SagaEndedEvent: 标志着saga事务请求的结束  成功场景下，全局事务事件SagaStartedEvent对应SagaEndedEvent ，每个子事务开始的事件TxStartedEvent都会有对应的结束事件TXEndedEvent。  -异常场景下，omega会向alpha上报中断事件TxAbortedEvent，然后alpha会向该全局事务的其它已成功的子事务(以完成TXEndedEvent)发送补偿指令，确保最终所有的子事务要么都成功，要么都回滚。 +异常场景下，Omega会向Alpha上报中断事件TxAbortedEvent，然后Alpha会根据全局事务的执行情况， 想其它已成功的子事务(以完成TXEndedEvent)的服务发送补偿指令，以确保最终所有的子事务要么都成功，要么都回滚。  -超时场景下，已超时的事件会被alpha的定期扫描器检测出来，与此同时，该超时事务对应的全局事务也会被中断。 - +超时场景下，已超时的事件会被alpha的定期扫描器检测出来，同时该超时事务对应的全局事务也会被中断。 +  1.用户发送Request请求调用业务方法(business logic) 2.preIntercept向alpha发送TxStartedEvent 3.被AOP拦截的方法(business logic)被调用 4.当执行成功时postIntercept发送TxEndedEvent到alpha 5.最后业务方法向用户发送response -基本运行机制清楚了，接下看具体实现的代码: -
[GitHub] [servicecomb-pack] jimforcode edited a comment on issue #327: io.grpc.StatusRuntimeException: CANCELLED: Failed to read message.
jimforcode edited a comment on issue #327: io.grpc.StatusRuntimeException: CANCELLED: Failed to read message. URL: https://github.com/apache/servicecomb-pack/issues/327#issuecomment-453068384 i‘ve solved this problem by excluding the dependency of springboot-dev-tools. It could change the classloader of omega which caused the issue. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] coolbeevip opened a new pull request #419: [SCB-1182] Modify the default activation profile spring-boot-2 in the document
coolbeevip opened a new pull request #419: [SCB-1182] Modify the default activation profile spring-boot-2 in the document URL: https://github.com/apache/servicecomb-pack/pull/419 Follow this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/SCB) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[SCB-XXX] Fixes bug in ApproximateQuantiles`, where you replace `SCB-XXX` with the appropriate JIRA issue. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean install` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] If this contribution is large, please file an Apache [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). --- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[servicecomb-docs] branch master updated (b424464 -> aab63a8)
This is an automated email from the ASF dual-hosted git repository.
ningjiang pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-docs.git.
from b424464 [SCB-1175] refactor the instructions for the configuration
mechanism
new 1167a21 add saga quick start
new 1713515 update quick start for issue
new 97602f2 update quick start saga logic
new da173b1 add workflow for saga quick start
new ef9d2e0 add saga mechanism with pic for quick start
new aab63a8 update saga mechanism and doc content
The 186 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
saga-reference/zh_CN/quickstart.md | 55 +
saga-reference/zh_CN/static_files/Exception.png| Bin 0 -> 166816 bytes
saga-reference/zh_CN/static_files/Success.png | Bin 0 -> 149671 bytes
saga-reference/zh_CN/static_files/Timeout.png | Bin 0 -> 61201 bytes
.../zh_CN/static_files/defaultRecovery.png | Bin 0 -> 72984 bytes
.../zh_CN/static_files/{pack.png => pack_arc.png} | Bin
saga-reference/zh_CN/static_files/pack_demo.png| Bin 0 -> 45374 bytes
7 files changed, 55 insertions(+)
create mode 100644 saga-reference/zh_CN/quickstart.md
create mode 100644 saga-reference/zh_CN/static_files/Exception.png
create mode 100644 saga-reference/zh_CN/static_files/Success.png
create mode 100644 saga-reference/zh_CN/static_files/Timeout.png
create mode 100644 saga-reference/zh_CN/static_files/defaultRecovery.png
copy saga-reference/zh_CN/static_files/{pack.png => pack_arc.png} (100%)
create mode 100644 saga-reference/zh_CN/static_files/pack_demo.png
[GitHub] [servicecomb-docs] WillemJiang merged pull request #77: add saga quick start
WillemJiang merged pull request #77: add saga quick start URL: https://github.com/apache/servicecomb-docs/pull/77 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] WillemJiang commented on issue #327: io.grpc.StatusRuntimeException: CANCELLED: Failed to read message.
WillemJiang commented on issue #327: io.grpc.StatusRuntimeException: CANCELLED: Failed to read message. URL: https://github.com/apache/servicecomb-pack/issues/327#issuecomment-469519965 I just added [a FAQ document](https://github.com/apache/servicecomb-pack/blob/master/docs/faq/en/omega-cannot-run-command-from-alpha.md) if you want to check out more information about it. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] WillemJiang closed issue #327: io.grpc.StatusRuntimeException: CANCELLED: Failed to read message.
WillemJiang closed issue #327: io.grpc.StatusRuntimeException: CANCELLED: Failed to read message. URL: https://github.com/apache/servicecomb-pack/issues/327 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[servicecomb-docs] branch master updated: [SCB-1175] refactor the instructions for the configuration mechanism
This is an automated email from the ASF dual-hosted git repository. wujimin pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/servicecomb-docs.git The following commit(s) were added to refs/heads/master by this push: new b424464 [SCB-1175] refactor the instructions for the configuration mechanism b424464 is described below commit b4244648723a8cb96d693a456c2176dd0ab04625 Author: yaohaishi AuthorDate: Mon Mar 4 21:49:32 2019 +0800 [SCB-1175] refactor the instructions for the configuration mechanism --- java-chassis-reference/en_US/SUMMARY.md| 3 +- java-chassis-reference/en_US/catalog/config.md | 2 + .../en_US/catalog/general-develop.md | 14 +--- .../en_US/config/general-config.md | 77 ++ .../en_US/general-development/config.md| 53 --- java-chassis-reference/zh_CN/SUMMARY.md| 3 +- java-chassis-reference/zh_CN/catalog/config.md | 2 + .../zh_CN/catalog/general-develop.md | 13 +--- .../zh_CN/config/general-config.md | 77 ++ .../zh_CN/general-development/config.md| 53 --- 10 files changed, 168 insertions(+), 129 deletions(-) diff --git a/java-chassis-reference/en_US/SUMMARY.md b/java-chassis-reference/en_US/SUMMARY.md index c1cad40..8ec9234 100644 --- a/java-chassis-reference/en_US/SUMMARY.md +++ b/java-chassis-reference/en_US/SUMMARY.md @@ -44,7 +44,6 @@ * [HTTP2](transports/http2.md) * [General Development](catalog/general-develop.md) * [Access Service Center](general-development/visit-sc.md) - * [Using Dynamic Configuration](general-development/config.md) * [Metrics](general-development/metrics.md) * [Microservice invocation chain](general-development/microservice-invocation-chain.md) * [Customized-Tracing](general-development/customized-tracing.md) @@ -66,6 +65,8 @@ * [Handling exceptions](general-development/error-handling.md) * [Multi-environment isolation between microservice instances](general-development/multienvironment.md) * [Thread Model](general-development/thread-model.md) +* [Configuration](catalog/config.md) + * [General config](config/general-config.md) * [Service Capability Open](edge/open-service.md) * [Using Edge Service](edge/by-servicecomb-sdk.md) * [Using confd and Nginx as edge services](edge/nginx.md) diff --git a/java-chassis-reference/en_US/catalog/config.md b/java-chassis-reference/en_US/catalog/config.md new file mode 100644 index 000..4fb5af5 --- /dev/null +++ b/java-chassis-reference/en_US/catalog/config.md @@ -0,0 +1,2 @@ +## General configuration instructions +Introduce the configuration hierarchy relationship and the usage of the configuration mechanism of ServiceComb-Java-Chassis. diff --git a/java-chassis-reference/en_US/catalog/general-develop.md b/java-chassis-reference/en_US/catalog/general-develop.md index ed109dd..2ce54fa 100644 --- a/java-chassis-reference/en_US/catalog/general-develop.md +++ b/java-chassis-reference/en_US/catalog/general-develop.md @@ -1,14 +1,6 @@ ## Access Service Center The system realizes the discovery between services through the service center. During the service startup process, the service center is registered. When calling other services, the service center will query the instance information of other services, such as the access address, the protocol used, and other parameters. The service center supports the use of PULL and PUSH modes to notify instance changes. - -## Using dynamic configuration -ServiceComb provides a hierarchical configuration mechanism. According to the priority, it is divided into: -• Configuration Center (dynamic configuration) -• Java System Property (-D parameter) -• Environmental variables -• Configuration file, microservice.yaml. The microservice.yaml file is scanned from the classpath and can be allowed to exist in many copies. Specify the priority by servicecomb-config-order. - ## Application Performance Monitoring 1. The introduction of Metrics 2. The summary of statistical items @@ -35,11 +27,11 @@ This section describes how to develop and debug consumer/provider applications l In some scenarios, the service uses http instead of https as the network transmission channel. In order to prevent the falsification or tampering request, the signature function of the http code stream between the consumer and the producer needs to be provided. -## File Upload +## File Upload File upload, currently supported in vertx rest channel and servlet rest. File uploads use the standard http form format, which interfaces directly with the browser's upload. -## Download Document +## Download Document File downloads are currently available in the vertx rest channel and servlet rest. @@ -78,4 +70,4 @@ Cross-Origin Resource Sharing (CORS) allows Web servers to perform cross-domain ## Obtaining the fuse and
[GitHub] [servicecomb-docs] wujimin merged pull request #87: [SCB-1175] refactor the instructions for the configuration mechanism
wujimin merged pull request #87: [SCB-1175] refactor the instructions for the configuration mechanism URL: https://github.com/apache/servicecomb-docs/pull/87 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] WillemJiang commented on issue #372: 我的服务模块连接不上alpha集群，以至于在全局事务时用restemplete 访问不了模块url
WillemJiang commented on issue #372: 我的服务模块连接不上alpha集群，以至于在全局事务时用restemplete 访问不了模块url URL: https://github.com/apache/servicecomb-pack/issues/372#issuecomment-469511842 if you want to access alpha-server.servicecomb.io, we need to setup the dns for it. Current we just leverage docker-compose to do the job, if you don't start the services from the **docker-compose**, you may face that kind of issue. The workaround could be modifying the host file of you box, but it could be a challenge for you as there are too much details need to be taken care of. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] WillemJiang closed issue #372: 我的服务模块连接不上alpha集群，以至于在全局事务时用restemplete 访问不了模块url
WillemJiang closed issue #372: 我的服务模块连接不上alpha集群，以至于在全局事务时用restemplete 访问不了模块url URL: https://github.com/apache/servicecomb-pack/issues/372 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] WillemJiang closed issue #211: dubbo demo运行问题
WillemJiang closed issue #211: dubbo demo运行问题 URL: https://github.com/apache/servicecomb-pack/issues/211 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] WillemJiang commented on issue #418: o.a.s.p.o.c.g.c.ReconnectStreamObserver : Failed to process grpc coordinate command.
WillemJiang commented on issue #418: o.a.s.p.o.c.g.c.ReconnectStreamObserver : Failed to process grpc coordinate command. URL: https://github.com/apache/servicecomb-pack/issues/418#issuecomment-469511472 Hi, Thx for report the issue, The omega-transport-feign issue had been fixed in #376 [SCB-1110](https://issues.apache.org/jira/browse/SCB-1110). For the stack trace I found there is an import information，which looks like the omega has some trouble to process the command message from Alpha. ``` Caused by: java.lang.NullPointerException: null at org.apache.servicecomb.pack.omega.context.CallbackContext$CallbackContextInternal.access$200(CallbackContext.java:63) at org.apache.servicecomb.pack.omega.context.CallbackContext.apply(CallbackContext.java:50) at org.apache.servicecomb.pack.omega.transaction.CompensationMessageHandler.onReceive(CompensationMessageHandler.java:35) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) at com.sun.proxy.$Proxy111.onReceive(Unknown Source) at org.apache.servicecomb.pack.omega.connector.grpc.saga.GrpcCompensateStreamObserver.onNext(GrpcCompensateStreamObserver.java:52) at org.apache.servicecomb.pack.omega.connector.grpc.saga.GrpcCompensateStreamObserver.onNext(GrpcCompensateStreamObserver.java:31) at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onMessage(ClientCalls.java:407) at io.grpc.ForwardingClientCallListener.onMessage(ForwardingClientCallListener.java:33) at io.grpc.ForwardingClientCallListener.onMessage(ForwardingClientCallListener.java:33) at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1MessagesAvailable.runInContext(ClientCallImpl.java:519) ... 5 common frames omitted ``` You may take a look at this [FAQ](https://github.com/apache/servicecomb-pack/blob/master/docs/faq/en/omega-cannot-run-command-from-alpha.md) to check if you have the same trouble here. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[servicecomb-pack] branch master updated: Added the new FAQ entry
This is an automated email from the ASF dual-hosted git repository. ningjiang pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/servicecomb-pack.git The following commit(s) were added to refs/heads/master by this push: new 0497507 Added the new FAQ entry 0497507 is described below commit 0497507170282145fcd4a2a5290c6ca427f6d742 Author: Willem Jiang AuthorDate: Tue Mar 5 10:29:10 2019 +0800 Added the new FAQ entry --- docs/faq/cn/omega-cannot-run-command-from-alpha.md | 34 ++ docs/faq/en/omega-cannot-run-command-from-alpha.md | 34 ++ 2 files changed, 68 insertions(+) diff --git a/docs/faq/cn/omega-cannot-run-command-from-alpha.md b/docs/faq/cn/omega-cannot-run-command-from-alpha.md new file mode 100644 index 000..7deed95 --- /dev/null +++ b/docs/faq/cn/omega-cannot-run-command-from-alpha.md @@ -0,0 +1,34 @@ + +**问题描述:** Omega客户端不执行Alpha服务端发出的命令 + +帮忙看下这个问题，Omega端能处理正常的调用，但是不执行Alpha服务端发送的指令， Alpha服务器没报错。 +服务的调用参数如下：使用字符串或者基本类型，还有map来传参数。 +我将参数涉及到的bean jar加入到Alpha中，Omega端还是报错，使用字符串或者基本类型，还有map来传参数，调用补偿方法都没问题。 + +报错信息： +``` +2019-01-07 19:25:39.983 WARN 18736 --- [nio-6060-exec-2] .m.m.a.ExceptionHandlerExceptionResolver : Resolved exception caused by handler execution: cn.com.aiidc.hicloud.component.bean.exception.HicloudException +2019-01-07 19:25:40.351 INFO 18736 --- [ault-executor-4] s.p.o.c.g.s.GrpcCompensateStreamObserver : Received compensate command, global tx id: 31c67d8e-1ced-4f70-83b6-7c151186120f, local tx id: a5cc191d-e50b-4c69-bb53-bb61309a1049, compensation method: public boolean cn.com.aiidc.hicloud.demo.service.impl.OrderServiceImpl.cancelCreateOrder(cn.com.aiidc.hicloud.component.bean.vo.order.CreateOrderVo) +2019-01-07 19:25:40.357 ERROR 18736 --- [ault-executor-4] o.a.s.p.o.c.g.c.ReconnectStreamObserver : Failed to process grpc coordinate command. +io.grpc.StatusRuntimeException: CANCELLED: Failed to read message. +at io.grpc.Status.asRuntimeException(Status.java:526) ~[grpc-core-1.14.0.jar:1.14.0] +at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:420) [grpc-stub-1.14.0.jar:1.14.0] +A +``` +解答： + +因为Alpha不会做反序列化的操作，其实添加cn.com.aiidc.hicloud.component.bean.vo.order.CreateOrderVo 这个类到Alpha中意义不大。 + +经过交流发现引入如下的依赖后造成的问题 + +``` + + org.springframework.boot + spring-boot-devtools + true + +``` + +maven去掉这个之后补偿方法正常调用了。详情参考： https://docs.spring.io/spring-boot/docs/current/reference/html/using-boot-devtools.html#using-boot-devtools-known-restart-limitations + +点评：引入spring-boot-devtools 会修改Omega对应的classloader，这样会造成omega寻找对应方法签名时出错。 diff --git a/docs/faq/en/omega-cannot-run-command-from-alpha.md b/docs/faq/en/omega-cannot-run-command-from-alpha.md new file mode 100644 index 000..76e1749 --- /dev/null +++ b/docs/faq/en/omega-cannot-run-command-from-alpha.md @@ -0,0 +1,34 @@ + +**Problem:** Omega does not run the command from Alpha + +We have a problem that Omega can pass the message to Alpha, but Omega cannot execute the command from Alpha. There is no error log from Alpha side, Omega keep complain about it failed to read the message from Alpha. +I tried to add the Omega method related module classes into Alpha, but Omega is keeping failed. The parameter are String and some other basic type, and we also use map in the parameter. + +Here is the stack trace from Omega side： + +``` +2019-01-07 19:25:39.983 WARN 18736 --- [nio-6060-exec-2] .m.m.a.ExceptionHandlerExceptionResolver : Resolved exception caused by handler execution: cn.com.aiidc.hicloud.component.bean.exception.HicloudException +2019-01-07 19:25:40.351 INFO 18736 --- [ault-executor-4] s.p.o.c.g.s.GrpcCompensateStreamObserver : Received compensate command, global tx id: 31c67d8e-1ced-4f70-83b6-7c151186120f, local tx id: a5cc191d-e50b-4c69-bb53-bb61309a1049, compensation method: public boolean cn.com.aiidc.hicloud.demo.service.impl.OrderServiceImpl.cancelCreateOrder(cn.com.aiidc.hicloud.component.bean.vo.order.CreateOrderVo) +2019-01-07 19:25:40.357 ERROR 18736 --- [ault-executor-4] o.a.s.p.o.c.g.c.ReconnectStreamObserver : Failed to process grpc coordinate command. +io.grpc.StatusRuntimeException: CANCELLED: Failed to read message. +at io.grpc.Status.asRuntimeException(Status.java:526) ~[grpc-core-1.14.0.jar:1.14.0] +at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:420) [grpc-stub-1.14.0.jar:1.14.0] +A +``` +Solution： + +Because of the Alpha does not unmarshal the message of the method parameter, adding the module classes into Alpha won't do any help. + +After talking with the user, we found it was caused by the dependency of below: + +``` + + org.springframework.boot + spring-boot-devtools + true + +``` + +The issue is gone when we remove the dependency from pom. +After checking the information https://docs.spring.io/spring-boot/docs/current/reference/html/using-boot-devtools.html#using-boot-devtools-known-restart-limitations
[servicecomb-pack] branch master updated: Updated the README files
This is an automated email from the ASF dual-hosted git repository. ningjiang pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/servicecomb-pack.git The following commit(s) were added to refs/heads/master by this push: new bf581f7 Updated the README files bf581f7 is described below commit bf581f73f08153ab022fc952292a82db0390aa12 Author: Willem Jiang AuthorDate: Tue Mar 5 09:56:00 2019 +0800 Updated the README files --- README.md| 10 +- README_ZH.md | 6 +++--- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index bbf0e2b..a3a6feb 100644 --- a/README.md +++ b/README.md @@ -39,16 +39,16 @@ Now we have different lanaguage implementation of Omega ``` * Build the source demo docker images and run the accept tests ```bash - $ mvn clean install -Pdemo,docker + $ mvn clean install -Pdemo ``` -* Build the source code and docker images without running tests +* Build the source code and docker images without running tests, the docker profile will be activated if the maven detects the docker installation. ```bash - $ mvn clean install -DskipTests=true -Pdemo,docker + $ mvn clean install -DskipTests=true -Pdemo ``` -* Current ServiceComb Pack code supports Spring Boot 1.x and Spring Boot 2.x at the same time, saga uses Spring Boot 2.x by default, you can use *-Pspring-boot-1* to switch Spring Boot version to 2.x. +* Current ServiceComb Pack code supports Spring Boot 1.x and Spring Boot 2.x at the same time, pack uses Spring Boot 2.x by default, you can use *-Pspring-boot-1* to switch Spring Boot version to 1.x. Since Spring Boot supports JDK9 since 2.x, if you want to build and run test the Saga with JDK9 or JDK10, please don't use the spring-boot-1 profile. ```bash - $ mvn clean install -Pdemo,docker,spring-boot-1 + $ mvn clean install -Pdemo,spring-boot-1 ``` ## User Guide diff --git a/README_ZH.md b/README_ZH.md index 89179df..d48fb48 100644 --- a/README_ZH.md +++ b/README_ZH.md @@ -40,9 +40,9 @@ ServiceComb Pack 架构是由 **alpha** 和 **omega**组成，其中： ```bash $ mvn clean install ``` -* 编译示例，并生产docker镜像，运行验收测试 +* 编译示例，并生成docker镜像（maven会根据是否安装docker来启动这部分的设置），运行验收测试。 ```bash - $ mvn clean install -Pdemo,docker + $ mvn clean install -Pdemo ``` * 编译示例，并生产docker镜像, 不运行测试 ```bash @@ -52,7 +52,7 @@ ServiceComb Pack 架构是由 **alpha** 和 **omega**组成，其中： 你可以使用 *-Pspring-boot-1* 将Spring Boot版本转换到 1.x 上。 由于Spring Boot 只在2.x开始支持 JDK9，如果你想用 JDK9或者JDK10来编译Saga并运行测试的话，请不要使用spring-boot-1 profile参数。 ```bash - $ mvn clean install -Pdemo,docker,spring-boot-1 + $ mvn clean install -Pdemo,spring-boot-1 ``` ## 用户指南
[servicecomb-pack] branch master updated: Polish the user guide document
This is an automated email from the ASF dual-hosted git repository.
ningjiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-pack.git
The following commit(s) were added to refs/heads/master by this push:
new f93cc3b Polish the user guide document
f93cc3b is described below
commit f93cc3b0deebaf3fbdde3a66620d8e7164731d30
Author: Willem Jiang
AuthorDate: Tue Mar 5 09:19:42 2019 +0800
Polish the user guide document
---
docs/user_guide_zh.md | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/docs/user_guide_zh.md b/docs/user_guide_zh.md
index 987b5a8..8829da3 100644
--- a/docs/user_guide_zh.md
+++ b/docs/user_guide_zh.md
@@ -213,11 +213,16 @@ Saga可通过以下任一方式进行构建：
然后就可以运行相关的微服务了，可通过访问http://${alpha-server:port}/saga/events 来获取所有的saga事件信息。
-### 注册中心支持
+## 在Alpha与Omega之间启用SSL
+
+详情请参考[启用 SSL](enable_ssl.md)文档.
+
+
+## 注册中心支持
支持Alpha启动时注册到发现服务，Omega通过发现服务获取Alpha的实例列表和gRPC地址
- Spring Cloud Eureka支持
+### Spring Cloud Eureka支持
1. 编译Alpha的Eureka的版本
[GitHub] [servicecomb-pack] WillemJiang commented on issue #333: install issue
WillemJiang commented on issue #333: install issue URL: https://github.com/apache/servicecomb-pack/issues/333#issuecomment-469494185 @wNee Did you still have some trouble to build the docker images of Alpha? I need to close this issue as there is no feedback for a long time, please let me know if you have any other question about it. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] WillemJiang closed issue #333: install issue
WillemJiang closed issue #333: install issue URL: https://github.com/apache/servicecomb-pack/issues/333 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] WillemJiang closed issue #334: docker-compose err:The image for the service you're trying to recreate has been removed
WillemJiang closed issue #334: docker-compose err:The image for the service you're trying to recreate has been removed URL: https://github.com/apache/servicecomb-pack/issues/334 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] WillemJiang commented on issue #334: docker-compose err:The image for the service you're trying to recreate has been removed
WillemJiang commented on issue #334: docker-compose err:The image for the service you're trying to recreate has been removed URL: https://github.com/apache/servicecomb-pack/issues/334#issuecomment-469493744 You can also build the docker image from the source with below command without running the test: `mvn clean install -DskipTests=true -Pdemo,docker' 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] coolbeevip commented on issue #418: o.a.s.p.o.c.g.c.ReconnectStreamObserver : Failed to process grpc coordinate command.
coolbeevip commented on issue #418: o.a.s.p.o.c.g.c.ReconnectStreamObserver : Failed to process grpc coordinate command. URL: https://github.com/apache/servicecomb-pack/issues/418#issuecomment-469491798 确实有这个问题，我看0.4.0版本已经修复了，我想0.3.0应该能很快修复 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] WillemJiang closed issue #393: NameResolver returned an empty list
WillemJiang closed issue #393: NameResolver returned an empty list URL: https://github.com/apache/servicecomb-pack/issues/393 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] WillemJiang commented on issue #393: NameResolver returned an empty list
WillemJiang commented on issue #393: NameResolver returned an empty list URL: https://github.com/apache/servicecomb-pack/issues/393#issuecomment-469490741 Close the issue as there is no feedback for a month. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[servicecomb-pack] branch master updated: Polish the user guide document
This is an automated email from the ASF dual-hosted git repository.
ningjiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-pack.git
The following commit(s) were added to refs/heads/master by this push:
new dbd772c Polish the user guide document
dbd772c is described below
commit dbd772ca9d39b3204b409de56c8180b3dac733fc
Author: Willem Jiang
AuthorDate: Tue Mar 5 08:50:13 2019 +0800
Polish the user guide document
---
docs/user_guide.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/user_guide.md b/docs/user_guide.md
index a0f2192..2778b8b 100644
--- a/docs/user_guide.md
+++ b/docs/user_guide.md
@@ -214,11 +214,11 @@ Then you can start your micro-services and access all
saga events via http://${a
See [Enabling SSL](enable_ssl.md) for details.
-### Service discovery support
+## Service discovery support
Alpha instance can register to the discovery service, Omega obtains Alpha's
instance list and gRPC address through discovery service
- Spring Cloud Eureka
+### Spring Cloud Eureka
1. build special version of Eureka
[GitHub] [servicecomb-pack] WillemJiang commented on issue #359: Alpha集群如何保证高可用？
WillemJiang commented on issue #359: Alpha集群如何保证高可用？ URL: https://github.com/apache/servicecomb-pack/issues/359#issuecomment-469488224 Hi, we introduced [a cluster service discovery management](https://github.com/apache/servicecomb-pack/blob/master/docs/user_guide.md#service-discovery-support) beside the Alpha Services, So I close the issue, please let us know if you have any other question about it. 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] WillemJiang closed issue #359: Alpha集群如何保证高可用？
WillemJiang closed issue #359: Alpha集群如何保证高可用？ URL: https://github.com/apache/servicecomb-pack/issues/359 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-java-chassis] wujimin merged pull request #1115: [SCB-1178]In the unit test, the issue of assertEquals and Float.MAX_VALUE.
wujimin merged pull request #1115: [SCB-1178]In the unit test, the issue of assertEquals and Float.MAX_VALUE. URL: https://github.com/apache/servicecomb-java-chassis/pull/1115 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-java-chassis] vanlin commented on issue #1114: 与Skywalking 6 GA整合发生错误！
vanlin commented on issue #1114: 与Skywalking 6 GA整合发生错误！ URL: https://github.com/apache/servicecomb-java-chassis/issues/1114#issuecomment-469480329 已经在 Skywalking 提交 issue https://github.com/apache/incubator-skywalking/issues/2308 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-docs] yhs0092 opened a new pull request #87: [SCB-1175] refactor the instructions for the configuration mechanism
yhs0092 opened a new pull request #87: [SCB-1175] refactor the instructions for the configuration mechanism URL: https://github.com/apache/servicecomb-docs/pull/87 For jira issue [SCB-1175](https://issues.apache.org/jira/browse/SCB-1175) 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [servicecomb-pack] xuanshu opened a new issue #418: o.a.s.p.o.c.g.c.ReconnectStreamObserver : Failed to process grpc coordinate command.
xuanshu opened a new issue #418: o.a.s.p.o.c.g.c.ReconnectStreamObserver : Failed to process grpc coordinate command. URL: https://github.com/apache/servicecomb-pack/issues/418 采用的是spring boot 1.X 版本 跨服务调用是采用的是springcloud feign ; serviceComb 是0.3.0 版本 （此版本omega-transport-feign 里面的spring.factories 文件需要改成由org.apache.servicecomb.saga.omega.transport.feign.FeignAutoConfiguration 改为org.apache.servicecomb.pack.omega.transport.feign.FeignAutoConfiguration 否则会报FeignAutoConfiguration 类找不到）； 会员服务调用消息服务没异常系统saga 不报错 ， 有异常则出现下面异常（主服务故意抛出异常，被调用服务则抛出下列异常） `2019-03-04 19:53:20.141 ERROR 53844 --- [ault-executor-2] o.a.s.p.o.c.g.c.ReconnectStreamObserver : Failed to process grpc coordinate command. io.grpc.StatusRuntimeException: CANCELLED: Failed to read message. at io.grpc.Status.asRuntimeException(Status.java:526) at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:420) at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39) at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23) at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40) at io.grpc.internal.CensusStatsModule$StatsClientInterceptor$1$1.onClose(CensusStatsModule.java:684) at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39) at io.grpc.ForwardingClientCallListener.onClose(ForwardingClientCallListener.java:23) at io.grpc.ForwardingClientCallListener$SimpleForwardingClientCallListener.onClose(ForwardingClientCallListener.java:40) at io.grpc.internal.CensusTracingModule$TracingClientInterceptor$1$1.onClose(CensusTracingModule.java:403) at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:459) at io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:63) at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:546) at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$600(ClientCallImpl.java:467) at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1MessagesAvailable.runInContext(ClientCallImpl.java:531) at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37) at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123) 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:748) Caused by: java.lang.NullPointerException: null at org.apache.servicecomb.pack.omega.context.CallbackContext$CallbackContextInternal.access$200(CallbackContext.java:63) at org.apache.servicecomb.pack.omega.context.CallbackContext.apply(CallbackContext.java:50) at org.apache.servicecomb.pack.omega.transaction.CompensationMessageHandler.onReceive(CompensationMessageHandler.java:35) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:333) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207) at com.sun.proxy.$Proxy111.onReceive(Unknown Source) at org.apache.servicecomb.pack.omega.connector.grpc.saga.GrpcCompensateStreamObserver.onNext(GrpcCompensateStreamObserver.java:52) at org.apache.servicecomb.pack.omega.connector.grpc.saga.GrpcCompensateStreamObserver.onNext(GrpcCompensateStreamObserver.java:31) at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onMessage(ClientCalls.java:407) at io.grpc.ForwardingClientCallListener.onMessage(ForwardingClientCallListener.java:33) at io.grpc.ForwardingClientCallListener.onMessage(ForwardingClientCallListener.java:33) at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1MessagesAvailable.runInContext(ClientCallImpl.java:519) ... 5 common frames omitted 03-04 19:53:20.141 ERROR [o.a.s.p.o.c.grpc.core.ReconnectStreamObserver] - Failed to process grpc coordinate command. io.grpc.StatusRuntimeException: CANCELLED: Failed to read message. at io.grpc.Status.asRuntimeException(Status.java:526) at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:420) at io.grpc.PartialForwardingClientCallListener.onClose(PartialForwardingClientCallListener.java:39) at
