[jira] [Created] (SCB-115) Security document translation
Bo Li created SCB-115: - Summary: Security document translation Key: SCB-115 URL: https://issues.apache.org/jira/browse/SCB-115 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li # Use TLS doc -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-113) Metrics document translation
Bo Li created SCB-113: - Summary: Metrics document translation Key: SCB-113 URL: https://issues.apache.org/jira/browse/SCB-113 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li Just Metrics document need to translate. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-114) Deployment document translation
Bo Li created SCB-114: - Summary: Deployment document translation Key: SCB-114 URL: https://issues.apache.org/jira/browse/SCB-114 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li # Run Mode doc -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-112) Edging Service document translation
Bo Li created SCB-112: - Summary: Edging Service document translation Key: SCB-112 URL: https://issues.apache.org/jira/browse/SCB-112 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li Edging Service document translation contains following part: # confd and Nginx # Zuul -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-111) General Development Translation
Bo Li created SCB-111: - Summary: General Development Translation Key: SCB-111 URL: https://issues.apache.org/jira/browse/SCB-111 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li General Development Translation contains following part: # Develop and Test in Local Environment # User ServiceComb in SpringBoot # Distribute Tracing # Customized Tracing -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-110) Develop Service Consumer Document Translation
Bo Li created SCB-110: - Summary: Develop Service Consumer Document Translation Key: SCB-110 URL: https://issues.apache.org/jira/browse/SCB-110 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li Develop Service Consumer Document Translation contains following part: # Develop with Rest Template # Develop with Transparent RPC # Use Service Contract # Invoke Control -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-109) Develop Service Provider Translation
Bo Li created SCB-109: - Summary: Develop Service Provider Translation Key: SCB-109 URL: https://issues.apache.org/jira/browse/SCB-109 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li Develop Service Provider translation contains: # Service Definition # Service Contract # Develop Microservice with SpringMVC # Develop Microservice with JAX-RS # Develop Microservice with Transparent-RPC # Service Interface Constraints # Service Configurations # Communicate Protocol # Application Boot Up Process # Service Heartbeat -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-108) User Guide Translation
Bo Li created SCB-108: - Summary: User Guide Translation Key: SCB-108 URL: https://issues.apache.org/jira/browse/SCB-108 Project: Apache ServiceComb Issue Type: Sub-task Components: website Reporter: Bo Li *User guide contains two part:* * Java Chassis Architecture * Setup Environment -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-107) Document Translation
Bo Li created SCB-107: - Summary: Document Translation Key: SCB-107 URL: https://issues.apache.org/jira/browse/SCB-107 Project: Apache ServiceComb Issue Type: Task Components: website Reporter: Bo Li There are some user guide document in Chinese need to be translated into English. Please refer to http://servicecomb.io/users/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-106) using @PostMapping and @RequestMapping(method=POST) given different interface definitions
liubao created SCB-106:
--
Summary: using @PostMapping and @RequestMapping(method=POST) given
different interface definitions
Key: SCB-106
URL: https://issues.apache.org/jira/browse/SCB-106
Project: Apache ServiceComb
Issue Type: Bug
Reporter: liubao
@RestSchema(schemaId = "test")
public class ComplexService {
@RequestMapping(path = "/", method = RequestMethod.POST)
public ResponseEntity custerInfo(@RequestBody CustomerInfoWrapper
info, HttpServletRequest request) {
ResponseEntity result =
ResponseEntity.ok(info.getData().getName());
return result;
}
}
given this schema:
basePath: "/ComplexService"
consumes:
- "application/json"
produces:
- "application/json"
paths:
/:
post:
operationId: "custerInfo"
parameters:
- in: "body"
name: "info"
required: false
schema:
$ref: "#/definitions/CustomerInfoWrapper"
responses:
200:
description: "response of 200"
schema:
type: "string"
but
@RestSchema(schemaId = "test")
public class ComplexService {
@PostMapping(path = "/")
public ResponseEntity custerInfo(@RequestBody CustomerInfoWrapper
info, HttpServletRequest request) {
ResponseEntity result =
ResponseEntity.ok(info.getData().getName());
return result;
}
}
given:
basePath: "/ComplexService"
consumes:
- "application/json"
produces:
- "application/json"
paths:
/custerInfo:
post:
operationId: "custerInfo"
parameters:
- in: "body"
name: "info"
required: false
schema:
$ref: "#/definitions/CustomerInfoWrapper"
responses:
200:
description: "response of 200"
schema:
$ref: "#/definitions/ResponseEntityString"
definitions:
CustomerInfo:
type: "object"
properties:
name:
type: "string"
x-java-class: "com.huawei.paas.cse.demo.springmvc.server.CustomerInfo"
CustomerInfoWrapper:
type: "object"
properties:
data:
$ref: "#/definitions/CustomerInfo"
x-java-class:
"com.huawei.paas.cse.demo.springmvc.server.CustomerInfoWrapper"
ResponseEntity:
type: "object"
properties:
headers:
type: "object"
additionalProperties:
type: "array"
items:
type: "string"
body:
type: "object"
statusCode:
type: "string"
enum:
- "CONTINUE"
- "SWITCHING_PROTOCOLS"
- "PROCESSING"
- "CHECKPOINT"
- "OK"
- "CREATED"
- "ACCEPTED"
- "NON_AUTHORITATIVE_INFORMATION"
- "NO_CONTENT"
- "RESET_CONTENT"
- "PARTIAL_CONTENT"
- "MULTI_STATUS"
- "ALREADY_REPORTED"
- "IM_USED"
- "MULTIPLE_CHOICES"
- "MOVED_PERMANENTLY"
ignored
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SCB-105) Invalid hyperlink at http://servicecomb.io/cn/developers/submit-codesI
Bo Li created SCB-105: - Summary: Invalid hyperlink at http://servicecomb.io/cn/developers/submit-codesI Key: SCB-105 URL: https://issues.apache.org/jira/browse/SCB-105 Project: Apache ServiceComb Issue Type: Bug Components: website Reporter: Bo Li Priority: Minor Hyperlink is not available after the project was moved to ApacheInfra. At http://servicecomb.io/cn/developers/submit-codes/ PR guild, Github, it jumps to old repository but not ApacheInfra. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-104) simplify transport rest template implementation
Eric Lee created SCB-104: Summary: simplify transport rest template implementation Key: SCB-104 URL: https://issues.apache.org/jira/browse/SCB-104 Project: Apache ServiceComb Issue Type: Task Components: Saga Reporter: Eric Lee Priority: Minor There already has a _exchange_ implementation in the_RestTemplateTransport_ which include the _get_ implementation. We can remove the _get_ method and add entry in the _exchange_ method for it. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-103) generate swagger from return java.util.concurrent.CompletableFuture method
wujimin created SCB-103: --- Summary: generate swagger from return java.util.concurrent.CompletableFuture method Key: SCB-103 URL: https://issues.apache.org/jira/browse/SCB-103 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: wujimin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-102) As a developer, I want to work in reactive mode to improve performance
wujimin created SCB-102: --- Summary: As a developer, I want to work in reactive mode to improve performance Key: SCB-102 URL: https://issues.apache.org/jira/browse/SCB-102 Project: Apache ServiceComb Issue Type: New Feature Components: Java-Chassis Reporter: wujimin -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SCB-100) [pack] async transaction support
[ https://issues.apache.org/jira/browse/SCB-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299420#comment-16299420 ] Yin Xiang commented on SCB-100: --- we need to pass tx id to threads executing the transaction > [pack] async transaction support > > > Key: SCB-100 > URL: https://issues.apache.org/jira/browse/SCB-100 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang > > as a dev, i want to be able to execute sub-transaction in a separate thread, > so that my service call is not blocked. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-101) [pack] design doc
Yin Xiang created SCB-101: - Summary: [pack] design doc Key: SCB-101 URL: https://issues.apache.org/jira/browse/SCB-101 Project: Apache ServiceComb Issue Type: New Feature Components: Saga Reporter: Yin Xiang -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-101) [pack] design doc
[ https://issues.apache.org/jira/browse/SCB-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yin Xiang reassigned SCB-101: - Assignee: Yin Xiang > [pack] design doc > - > > Key: SCB-101 > URL: https://issues.apache.org/jira/browse/SCB-101 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Saga >Reporter: Yin Xiang >Assignee: Yin Xiang > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-100) [pack] async transaction support
Yin Xiang created SCB-100: - Summary: [pack] async transaction support Key: SCB-100 URL: https://issues.apache.org/jira/browse/SCB-100 Project: Apache ServiceComb Issue Type: New Feature Components: Saga Reporter: Yin Xiang as a dev, i want to be able to execute sub-transaction in a separate thread, so that my service call is not blocked. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-99) [pack] compensate on transaction timeout
Yin Xiang created SCB-99: Summary: [pack] compensate on transaction timeout Key: SCB-99 URL: https://issues.apache.org/jira/browse/SCB-99 Project: Apache ServiceComb Issue Type: New Feature Components: Saga Reporter: Yin Xiang as a user, i want to compensate all completed transactions on timeout, so that the involved services are consistent. alpha tells omegas to compensate on timeout -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-98) [pack] compensate on transaction failure
Yin Xiang created SCB-98: Summary: [pack] compensate on transaction failure Key: SCB-98 URL: https://issues.apache.org/jira/browse/SCB-98 Project: Apache ServiceComb Issue Type: New Feature Components: Saga Reporter: Yin Xiang as a user, i want to compensate all completed transactions on failure, so that the involved services are consistent. alpha tells omegas to compensate -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-97) [pack] update alpha about transaction state
Yin Xiang created SCB-97: Summary: [pack] update alpha about transaction state Key: SCB-97 URL: https://issues.apache.org/jira/browse/SCB-97 Project: Apache ServiceComb Issue Type: New Feature Components: Saga Reporter: Yin Xiang as a dev, i want to store transaction states in a centralized place, so that i can decouple transaction management from service business logic. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-96) [pack] intercept sub-transaction commits
Yin Xiang created SCB-96: Summary: [pack] intercept sub-transaction commits Key: SCB-96 URL: https://issues.apache.org/jira/browse/SCB-96 Project: Apache ServiceComb Issue Type: New Feature Components: Saga Reporter: Yin Xiang as a dev, i want to intercept *around* transaction commits in a service, so that i can do some custom processing before & after the transaction is performed -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-95) [pack] able to link sub-transactions as a single global transaction
Yin Xiang created SCB-95: Summary: [pack] able to link sub-transactions as a single global transaction Key: SCB-95 URL: https://issues.apache.org/jira/browse/SCB-95 Project: Apache ServiceComb Issue Type: New Feature Components: Saga Reporter: Yin Xiang as a dev, i want to know which sub-transactions are contained in a global transaction, so that i can manage their states together -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (SCB-6) ServiceComb Java Chassis Metrics
[
https://issues.apache.org/jira/browse/SCB-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297949#comment-16297949
]
yangyongzheng edited comment on SCB-6 at 12/21/17 2:00 AM:
---
*What this the progress?*
1. EventBus in Java Chassis
{color:red}Completed{color}
2. Metrics core module
{color:red}Completed{color}
3. Implement CallCount and TPS Metrics
{color:red}PR Submitted{color}
4. Implement Runtime System Resources Usage Metrics
{color:red}PR Submitted{color}
5. Metrics Auto Publish
{color:red}PR Submitted{color}
6. Support Custom Metrics
{color:red}TO DO{color}
7. Upgrade Metrics File Output from 0.5.0 to 0.6.0
{color:red}Coding{color}
8. All Monitor can convert to Map with plain-key when polling data
{color:red}Coding{color}
*What is the next?*
Process 78
*How much percent have you done?*
60%
was (Author: zhengyangyong):
*What this the progress?*
1. EventBus in Java Chassis
{color:red}Completed{color}
2. Metrics core module
{color:red}Completed{color}
3. Implement CallCount and TPS Metrics
{color:red}PR Submitted {color}
4. Implement Runtime System Resources Usage Metrics
{color:red}PR Submitted PR{color}
5. Metrics Auto Publish
{color:red}PR Submitted{color}
6. Support Custom Metrics
{color:red}TO DO{color}
7. Upgrade Metrics File Output from 0.5.0 to 0.6.0
{color:red}Coding{color}
8. All Monitor can convert to Map with plain-key when polling data
{color:red}Coding{color}
*What is the next?*
Process 78
*How much percent have you done?*
60%
> ServiceComb Java Chassis Metrics
>
>
> Key: SCB-6
> URL: https://issues.apache.org/jira/browse/SCB-6
> Project: Apache ServiceComb
> Issue Type: New Feature
> Components: Java-Chassis
>Reporter: yangyongzheng
>Assignee: yangyongzheng
>
> As a microservice framework,servicecomb java chassis need support user
> collect metrics such as tps,latency and system resource usage etc,then use
> this collected data making some policy like scaling strategy further.
> The relation between Java Chassis and Java Chassis Metrics is similar to
> Spring boot and Spring boot actuator.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SCB-6) ServiceComb Java Chassis Metrics
[
https://issues.apache.org/jira/browse/SCB-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297949#comment-16297949
]
yangyongzheng edited comment on SCB-6 at 12/21/17 1:59 AM:
---
*What this the progress?*
1. EventBus in Java Chassis
{color:red}Completed{color}
2. Metrics core module
{color:red}Completed{color}
3. Implement CallCount and TPS Metrics
{color:red}PR Submitted {color}
4. Implement Runtime System Resources Usage Metrics
{color:red}PR Submitted PR{color}
5. Metrics Auto Publish
{color:red}PR Submitted{color}
6. Support Custom Metrics
{color:red}TO DO{color}
7. Upgrade Metrics File Output from 0.5.0 to 0.6.0
{color:red}Coding{color}
8. All Monitor can convert to Map with plain-key when polling data
{color:red}Coding{color}
*What is the next?*
Process 78
*How much percent have you done?*
60%
was (Author: zhengyangyong):
*What this the progress?*
1. EventBus in Java Chassis
{color:red}Completed{color}
2. Metrics core module
{color:red}Completed{color}
3. Implement CallCount and TPS Metrics
{color:red}PR Submitted {color}
4. Implement Runtime System Resources Usage Metrics
{color:red}PR Submitted PR{color}
5. Metrics Auto Publish
{color:red}PR Submitted{color}
6. Support Custom Metrics
{color:red}TO DO{color}
*What is the next?*
Submit PR of 345 after 2 Merged,Design 6
*How much percent have you done?*
60%
> ServiceComb Java Chassis Metrics
>
>
> Key: SCB-6
> URL: https://issues.apache.org/jira/browse/SCB-6
> Project: Apache ServiceComb
> Issue Type: New Feature
> Components: Java-Chassis
>Reporter: yangyongzheng
>Assignee: yangyongzheng
>
> As a microservice framework,servicecomb java chassis need support user
> collect metrics such as tps,latency and system resource usage etc,then use
> this collected data making some policy like scaling strategy further.
> The relation between Java Chassis and Java Chassis Metrics is similar to
> Spring boot and Spring boot actuator.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Comment Edited] (SCB-6) ServiceComb Java Chassis Metrics
[
https://issues.apache.org/jira/browse/SCB-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16297949#comment-16297949
]
yangyongzheng edited comment on SCB-6 at 12/21/17 1:58 AM:
---
*What this the progress?*
1. EventBus in Java Chassis
{color:red}Completed{color}
2. Metrics core module
{color:red}Completed{color}
3. Implement CallCount and TPS Metrics
{color:red}PR Submitted {color}
4. Implement Runtime System Resources Usage Metrics
{color:red}PR Submitted PR{color}
5. Metrics Auto Publish
{color:red}PR Submitted{color}
6. Support Custom Metrics
{color:red}TO DO{color}
*What is the next?*
Submit PR of 345 after 2 Merged,Design 6
*How much percent have you done?*
60%
was (Author: zhengyangyong):
*What this the progress?*
1. EventBus in Java Chassis
{color:red}Completed{color}
2. Metrics core module
{color:red}Wait Merge{color}
3. Implement CallCount and TPS Metrics
{color:red}Wait Submit PR{color}
4. Implement Runtime System Resources Usage Metrics
{color:red}Wait Submit PR{color}
5. Metrics Auto Publish
{color:red}Wait Submit PR{color}
6. Support Custom Metrics
{color:red}TO DO{color}
*What is the next?*
Submit PR of 345 after 2 Merged,Design 6
*How much percent have you done?*
50%
> ServiceComb Java Chassis Metrics
>
>
> Key: SCB-6
> URL: https://issues.apache.org/jira/browse/SCB-6
> Project: Apache ServiceComb
> Issue Type: New Feature
> Components: Java-Chassis
>Reporter: yangyongzheng
>Assignee: yangyongzheng
>
> As a microservice framework,servicecomb java chassis need support user
> collect metrics such as tps,latency and system resource usage etc,then use
> this collected data making some policy like scaling strategy further.
> The relation between Java Chassis and Java Chassis Metrics is similar to
> Spring boot and Spring boot actuator.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (SCB-36) Support connecting to the third party dynamic config center
[ https://issues.apache.org/jira/browse/SCB-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Willem Jiang reassigned SCB-36: --- Assignee: Willem Jiang > Support connecting to the third party dynamic config center > --- > > Key: SCB-36 > URL: https://issues.apache.org/jira/browse/SCB-36 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: mabin >Assignee: Willem Jiang > > Java-chassis can connect to another open source config center to support > changing the setting dynamically. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SCB-11) Metrics Auto Publish
[ https://issues.apache.org/jira/browse/SCB-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299387#comment-16299387 ] yangyongzheng commented on SCB-11: -- PR已提交，https://github.com/ApacheInfra/ServiceComb-Java-Chassis/pull/453 > Metrics Auto Publish > > > Key: SCB-11 > URL: https://issues.apache.org/jira/browse/SCB-11 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: yangyongzheng >Assignee: yangyongzheng > > If user include metrics in dependency,the metrics service would auto publish > with Java Chassis Producer,also use same transport and endpoint config. > For example if user config rest address 0.0.0.0:8080 in > microservice.yaml,then the metrics service will available at http:// address>:8080/metrics -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SCB-10) Implement Runtime System Resources Usage Metrics
[ https://issues.apache.org/jira/browse/SCB-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299367#comment-16299367 ] yangyongzheng commented on SCB-10: -- PR已提交，https://github.com/ApacheInfra/ServiceComb-Java-Chassis/pull/452 > Implement Runtime System Resources Usage Metrics > > > Key: SCB-10 > URL: https://issues.apache.org/jira/browse/SCB-10 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: yangyongzheng >Assignee: yangyongzheng > > In core module we need add more build-in Metrics,include: > 1.CPU usage > 2.Heap usage > 3.Nonheap usage > 4.Running thread count -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SCB-9) Implement CallCount and TPS Metrics
[ https://issues.apache.org/jira/browse/SCB-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16299365#comment-16299365 ] yangyongzheng commented on SCB-9: - PR已经提交，https://github.com/ApacheInfra/ServiceComb-Java-Chassis/pull/451/files > Implement CallCount and TPS Metrics > --- > > Key: SCB-9 > URL: https://issues.apache.org/jira/browse/SCB-9 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: yangyongzheng >Assignee: yangyongzheng > > In core module we need add more build-in Metrics,include: > 1.consumer total call count > 2.provider total call count > 3.consumer call tps > 4.provider call tps -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SCB-8) Metrics core module
[ https://issues.apache.org/jira/browse/SCB-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng resolved SCB-8. - Resolution: Fixed PR merged https://github.com/ApacheInfra/ServiceComb-Java-Chassis/pull/399 > Metrics core module > --- > > Key: SCB-8 > URL: https://issues.apache.org/jira/browse/SCB-8 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: yangyongzheng >Assignee: yangyongzheng > > Add a new Module named "metrics-core" in ServiceComb Java Chassis as Metrics > major architecture, and provide basic latency data ,include : > 1.life time in queue > 2.producer execute time (run operation logic) > 3.producer total time (producer latency) > 4.consumer total time (consumer latency) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-21) service orchestration
[ https://issues.apache.org/jira/browse/SCB-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin reassigned SCB-21: - Assignee: (was: Zhinan Lin) > service orchestration > - > > Key: SCB-21 > URL: https://issues.apache.org/jira/browse/SCB-21 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: Eric Lee > Attachments: Proposal for integrating ServiceComb into Camel.pdf > > > orchestration of service invocation and aggregation of data from multiple > services based on configured rule > eg. a user request requires calling service a/b/c/d in order: request -> a -> > b -> c -> d -> response > this creates a tight coupling among services a/b/c/d. > better solutions: > request -> aggregator -> response (aggregator calls a/b/c/d in sequence based > on configured rule) > request -> a -> message queue -> b -> queue -> c -> queue -> d > both ways no coupling among the services. > this epic is about solution 1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-21) service orchestration
[ https://issues.apache.org/jira/browse/SCB-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhinan Lin reassigned SCB-21: - Assignee: Zhinan Lin > service orchestration > - > > Key: SCB-21 > URL: https://issues.apache.org/jira/browse/SCB-21 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: Eric Lee >Assignee: Zhinan Lin > Attachments: Proposal for integrating ServiceComb into Camel.pdf > > > orchestration of service invocation and aggregation of data from multiple > services based on configured rule > eg. a user request requires calling service a/b/c/d in order: request -> a -> > b -> c -> d -> response > this creates a tight coupling among services a/b/c/d. > better solutions: > request -> aggregator -> response (aggregator calls a/b/c/d in sequence based > on configured rule) > request -> a -> message queue -> b -> queue -> c -> queue -> d > both ways no coupling among the services. > this epic is about solution 1 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SCB-91) All Monitor can convert to Map with plain-key when polling data
[
https://issues.apache.org/jira/browse/SCB-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Lee reassigned SCB-91:
---
Assignee: yangyongzheng
> All Monitor can convert to Map with plain-key when polling data
> ---
>
> Key: SCB-91
> URL: https://issues.apache.org/jira/browse/SCB-91
> Project: Apache ServiceComb
> Issue Type: Sub-task
> Components: Java-Chassis
>Reporter: yangyongzheng
>Assignee: yangyongzheng
>
> Because sample like output file need write metrics into separate files,it's
> better get plain-key Map contains all metrics data rather than get metric
> model.
> This also can use in publish metrics with plain-key mode like Spring boot
> actuator act:
> { "counter.status.200.root": 20, "counter.status.200.metrics": 3,
> "counter.status.200.star-star": 5, "counter.status.401.root": 4,
> "gauge.response.star-star": 6, "gauge.response.root": 2,
> "gauge.response.metrics": 3, "classes": 5808, "classes.loaded": 5808,
> "classes.unloaded": 0, "heap": 3728384, "heap.committed": 986624,
> "heap.init": 262144, "heap.used": 52765, "nonheap": 0, "nonheap.committed":
> 77568, "nonheap.init": 2496, "nonheap.used": 75826, "mem": 986624,
> "mem.free": 933858, "processors": 8, "threads": 15, "threads.daemon": 11,
> "threads.peak": 15, "threads.totalStarted": 42, "uptime": 494836,
> "instance.uptime": 489782, "datasource.primary.active": 5,
> "datasource.primary.usage": 0.25 }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SCB-94) How about changing the log module to logus or other opensource project?
Bo Li created SCB-94: Summary: How about changing the log module to logus or other opensource project? Key: SCB-94 URL: https://issues.apache.org/jira/browse/SCB-94 Project: Apache ServiceComb Issue Type: Bug Components: Service-Center Reporter: Bo Li How about to change the log module to logus or other opensource project? https://github.com/ServiceComb/service-center/tree/master/lager -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-93) inconsistent configuration folders
Bo Li created SCB-93: Summary: inconsistent configuration folders Key: SCB-93 URL: https://issues.apache.org/jira/browse/SCB-93 Project: Apache ServiceComb Issue Type: Bug Components: Service-Center Reporter: Bo Li he certificates stores under etc/ssl folder, while the application configuration files stores under conf folder, which looks inconsistent. Is it a better idea to merge both of it under etc folder? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-92) ip port was wrong when tesing schema
Bo Li created SCB-92: Summary: ip port was wrong when tesing schema Key: SCB-92 URL: https://issues.apache.org/jira/browse/SCB-92 Project: Apache ServiceComb Issue Type: Bug Components: Service-Center Reporter: Bo Li ( Error while sending request due to : Post http://10.63.185.117:2087/appServiceImpl2/queryApplicationFromInner: dial tcp 10.63.185.117:2087: connectex: No connection could be made because the target machine actively refused it. 20879 and 2087 confusing me! -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SCB-91) All Monitor can convert to Map with plain-key when polling data
[
https://issues.apache.org/jira/browse/SCB-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yangyongzheng updated SCB-91:
-
Description:
Because sample like output file need write metrics into separate files,it's
better get plain-key Map contains all metrics data rather than get metric model.
This also can use in publish metrics with plain-key mode like Spring boot
actuator act:
{ "counter.status.200.root": 20, "counter.status.200.metrics": 3,
"counter.status.200.star-star": 5, "counter.status.401.root": 4,
"gauge.response.star-star": 6, "gauge.response.root": 2,
"gauge.response.metrics": 3, "classes": 5808, "classes.loaded": 5808,
"classes.unloaded": 0, "heap": 3728384, "heap.committed": 986624, "heap.init":
262144, "heap.used": 52765, "nonheap": 0, "nonheap.committed": 77568,
"nonheap.init": 2496, "nonheap.used": 75826, "mem": 986624, "mem.free": 933858,
"processors": 8, "threads": 15, "threads.daemon": 11, "threads.peak": 15,
"threads.totalStarted": 42, "uptime": 494836, "instance.uptime": 489782,
"datasource.primary.active": 5, "datasource.primary.usage": 0.25 }
was:
Because sample like output file need write metrics into separate files,it's
better get plain-key Map contains all metrics data rather than get metric model.
This also can use in publish metrics with plain-key mode like Spring boot
actuator act:
_{ "counter.status.200.root": 20, "counter.status.200.metrics": 3,
"counter.status.200.star-star": 5, "counter.status.401.root": 4,
"gauge.response.star-star": 6, "gauge.response.root": 2,
"gauge.response.metrics": 3, "classes": 5808, "classes.loaded": 5808,
"classes.unloaded": 0, "heap": 3728384, "heap.committed": 986624, "heap.init":
262144, "heap.used": 52765, "nonheap": 0, "nonheap.committed": 77568,
"nonheap.init": 2496, "nonheap.used": 75826, "mem": 986624, "mem.free": 933858,
"processors": 8, "threads": 15, "threads.daemon": 11, "threads.peak": 15,
"threads.totalStarted": 42, "uptime": 494836, "instance.uptime": 489782,
"datasource.primary.active": 5, "datasource.primary.usage": 0.25 }_
> All Monitor can convert to Map with plain-key when polling data
> ---
>
> Key: SCB-91
> URL: https://issues.apache.org/jira/browse/SCB-91
> Project: Apache ServiceComb
> Issue Type: Sub-task
> Components: Java-Chassis
>Reporter: yangyongzheng
>
> Because sample like output file need write metrics into separate files,it's
> better get plain-key Map contains all metrics data rather than get metric
> model.
> This also can use in publish metrics with plain-key mode like Spring boot
> actuator act:
> { "counter.status.200.root": 20, "counter.status.200.metrics": 3,
> "counter.status.200.star-star": 5, "counter.status.401.root": 4,
> "gauge.response.star-star": 6, "gauge.response.root": 2,
> "gauge.response.metrics": 3, "classes": 5808, "classes.loaded": 5808,
> "classes.unloaded": 0, "heap": 3728384, "heap.committed": 986624,
> "heap.init": 262144, "heap.used": 52765, "nonheap": 0, "nonheap.committed":
> 77568, "nonheap.init": 2496, "nonheap.used": 75826, "mem": 986624,
> "mem.free": 933858, "processors": 8, "threads": 15, "threads.daemon": 11,
> "threads.peak": 15, "threads.totalStarted": 42, "uptime": 494836,
> "instance.uptime": 489782, "datasource.primary.active": 5,
> "datasource.primary.usage": 0.25 }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SCB-91) All Monitor can convert to Map with plain-key when polling data
yangyongzheng created SCB-91:
Summary: All Monitor can convert to Map with plain-key when
polling data
Key: SCB-91
URL: https://issues.apache.org/jira/browse/SCB-91
Project: Apache ServiceComb
Issue Type: Sub-task
Reporter: yangyongzheng
Because sample like output file need write metrics into separate files,it's
better get plain-key Map contains all metrics data rather than get metric model.
This also can use in publish metrics with plain-key mode like Spring boot
actuator act:
_{ "counter.status.200.root": 20, "counter.status.200.metrics": 3,
"counter.status.200.star-star": 5, "counter.status.401.root": 4,
"gauge.response.star-star": 6, "gauge.response.root": 2,
"gauge.response.metrics": 3, "classes": 5808, "classes.loaded": 5808,
"classes.unloaded": 0, "heap": 3728384, "heap.committed": 986624, "heap.init":
262144, "heap.used": 52765, "nonheap": 0, "nonheap.committed": 77568,
"nonheap.init": 2496, "nonheap.used": 75826, "mem": 986624, "mem.free": 933858,
"processors": 8, "threads": 15, "threads.daemon": 11, "threads.peak": 15,
"threads.totalStarted": 42, "uptime": 494836, "instance.uptime": 489782,
"datasource.primary.active": 5, "datasource.primary.usage": 0.25 }_
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SCB-90) Failed to deploy frontend Service center on Huawei Cloud
Bo Li created SCB-90: Summary: Failed to deploy frontend Service center on Huawei Cloud Key: SCB-90 URL: https://issues.apache.org/jira/browse/SCB-90 Project: Apache ServiceComb Issue Type: Bug Components: Service-Center Environment: ServiceCenter docker image is already runing on ServiceStage Reporter: Bo Li Deploy frontend service center on public Huawei Cloud, it fails, # deploy: frontend-service-center-0.4.0-linux-amd64.tar.gz, run as vm app, sh start.sh and sh stop.sh # error information: create processes failed: failed to "StartProcess" for "process1" with ExecuteCommandFailed: "error info: exit status 127 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-89) Restart local service-center and service-center hung
Bo Li created SCB-89: Summary: Restart local service-center and service-center hung Key: SCB-89 URL: https://issues.apache.org/jira/browse/SCB-89 Project: Apache ServiceComb Issue Type: Bug Components: Service-Center Reporter: Bo Li # Download service-center-0.4.0-linux-amd64.tar.gz # Execute start.sh # Send CTRL+C after SC is ready # Execute start.sh again # And SC hung for some reasons. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SCB-88) error occurs when start a service following "quick start"
[
https://issues.apache.org/jira/browse/SCB-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bo Li updated SCB-88:
-
Component/s: Java-Chassis
> error occurs when start a service following "quick start"
> -
>
> Key: SCB-88
> URL: https://issues.apache.org/jira/browse/SCB-88
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>
> {code}
> java.net.ConnectException: Failed to connect to /127.0.0.1:9411
> at
> okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:189)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.RealConnection.buildConnection(RealConnection.java:173)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.RealConnection.connect(RealConnection.java:114)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:193)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:129)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:98)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:109)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:124)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
> ~[okhttp-3.4.1.jar:na]
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:170)
> ~[okhttp-3.4.1.jar:na]
> at okhttp3.RealCall.access$100(RealCall.java:33) ~[okhttp-3.4.1.jar:na]
> at okhttp3.RealCall$AsyncCall.execute(RealCall.java:120)
> ~[okhttp-3.4.1.jar:na]
> at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
> [okhttp-3.4.1.jar:na]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [na:1.8.0_121]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_121]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_121]
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SCB-88) error occurs when start a service following "quick start"
Bo Li created SCB-88:
Summary: error occurs when start a service following "quick start"
Key: SCB-88
URL: https://issues.apache.org/jira/browse/SCB-88
Project: Apache ServiceComb
Issue Type: Bug
Reporter: Bo Li
{code}
java.net.ConnectException: Failed to connect to /127.0.0.1:9411
at
okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:189)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.connection.RealConnection.buildConnection(RealConnection.java:173)
~[okhttp-3.4.1.jar:na]
at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:114)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:193)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:129)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:98)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
~[okhttp-3.4.1.jar:na]
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:109)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
~[okhttp-3.4.1.jar:na]
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:124)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
~[okhttp-3.4.1.jar:na]
at
okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
~[okhttp-3.4.1.jar:na]
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:170)
~[okhttp-3.4.1.jar:na]
at okhttp3.RealCall.access$100(RealCall.java:33) ~[okhttp-3.4.1.jar:na]
at okhttp3.RealCall$AsyncCall.execute(RealCall.java:120) ~[okhttp-3.4.1.jar:na]
at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
[okhttp-3.4.1.jar:na]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
[na:1.8.0_121]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
[na:1.8.0_121]
at java.lang.Thread.run(Thread.java:745) [na:1.8.0_121]
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SCB-87) can anyone provide a gradle script?
Bo Li created SCB-87: Summary: can anyone provide a gradle script? Key: SCB-87 URL: https://issues.apache.org/jira/browse/SCB-87 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Reporter: Bo Li -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-86) can not find handler :tracing-provider
Bo Li created SCB-86:
Summary: can not find handler :tracing-provider
Key: SCB-86
URL: https://issues.apache.org/jira/browse/SCB-86
Project: Apache ServiceComb
Issue Type: Bug
Components: Java-Chassis
Reporter: Bo Li
{code}java.lang.Error: can not find handler: tracing-project {code} error
occurs when runing bmi distributed tracing demo.
microservice.yaml configuration is:
{code}
APPLICATION_ID: bmi
service_description:
# name of the declaring microservice
name: calculator
version: 0.0.1
cse:
service:
registry:
address: http://127.0.0.1:30100
rest:
address: 0.0.0.0:
handler:
chain:
Provider:
default: tracing-provider
{code}
exception throwed when runing CalculationApplication:
{code}
2017-09-19 11:57:28,586 [ERROR] Application startup failed
org.springframework.boot.SpringApplication.reportFailure(SpringApplication.java:840)
java.lang.Error: can not find handler :tracing-provider
at
io.servicecomb.core.handler.AbstractHandlerManager.convertToChainClass(AbstractHandlerManager.java:68)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.handler.AbstractHandlerManager.createHandlerChain(AbstractHandlerManager.java:82)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.handler.AbstractHandlerManager.create(AbstractHandlerManager.java:110)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.handler.AbstractHandlerManager.create(AbstractHandlerManager.java:32)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.foundation.common.AbstractObjectManager.getOrCreate(AbstractObjectManager.java:36)
~[foundation-common-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.definition.loader.SchemaLoader.registerSchema(SchemaLoader.java:94)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:112)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:42)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.definition.schema.AbstractSchemaFactory.getOrCreateSchema(AbstractSchemaFactory.java:59)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.definition.schema.ProducerSchemaFactory.getOrCreateProducerSchema(ProducerSchemaFactory.java:75)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.provider.rest.common.RestProducerProvider.init(RestProducerProvider.java:48)
~[provider-rest-common-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.provider.producer.ProducerProviderManager.init(ProducerProviderManager.java:43)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
io.servicecomb.core.CseApplicationListener.onApplicationEvent(CseApplicationListener.java:113)
~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
at
org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:166)
~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
at
org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:138)
~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:383)
~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:337)
~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
at
org.springframework.boot.context.event.EventPublishingRunListener.finished(EventPublishingRunListener.java:99)
~[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
at
org.springframework.boot.SpringApplicationRunListeners.callFinishedListener(SpringApplicationRunListeners.java:79)
~[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
at
org.springframework.boot.SpringApplicationRunListeners.finished(SpringApplicationRunListeners.java:72)
~[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:318)
[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:1187)
[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
at
org.springframework.boot.SpringApplication.run(SpringApplication.java:1176)
[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
at
io.servicecomb.samples.bmi.CalculatorApplication.main(CalculatorApplication.java:29)
[classes/:?]
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (SCB-85) Upgrade Metrics File Output from 0.5.0 to 0.6.0
[ https://issues.apache.org/jira/browse/SCB-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-85: Assignee: yangyongzheng > Upgrade Metrics File Output from 0.5.0 to 0.6.0 > --- > > Key: SCB-85 > URL: https://issues.apache.org/jira/browse/SCB-85 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: yangyongzheng >Assignee: yangyongzheng > > Because metrics had complete reflected in 0.6.0,so we need upgrade file > output example and show new features. > 1.support more build-in metric > 2.support output operation level metrc -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-85) Upgrade Metrics File Output from 0.5.0 to 0.6.0
yangyongzheng created SCB-85: Summary: Upgrade Metrics File Output from 0.5.0 to 0.6.0 Key: SCB-85 URL: https://issues.apache.org/jira/browse/SCB-85 Project: Apache ServiceComb Issue Type: Sub-task Reporter: yangyongzheng Because metrics had complete reflected in 0.6.0,so we need upgrade file output example and show new features. 1.support more build-in metric 2.support output operation level metrc -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-84) Is there a interface for user to find service according to schemaId
Bo Li created SCB-84: Summary: Is there a interface for user to find service according to schemaId Key: SCB-84 URL: https://issues.apache.org/jira/browse/SCB-84 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Reporter: Bo Li -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SCB-83) BMI Calculator throws exception
Bo Li created SCB-83:
Summary: BMI Calculator throws exception
Key: SCB-83
URL: https://issues.apache.org/jira/browse/SCB-83
Project: Apache ServiceComb
Issue Type: Bug
Components: Java-Chassis
Reporter: Bo Li
when running BMI Calculator repeatly, it throws:
{code}
Internal Server Error: com.netflix.zuul.exception.ZuulException
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
