[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

[jira] [Resolved] (SCB-503) When using WeighedResponseTimeRule, there are some initialize and stateless access problems

[ https://issues.apache.org/jira/browse/SCB-503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-503. Resolution: Fixed Fix Version/s: java-chassis-1.0.0-m2 > When using WeighedResponseTimeRule, there are some

[jira] [Resolved] (SCB-517) service center starter for spring boot/cloud improvement

[ https://issues.apache.org/jira/browse/SCB-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-517. Resolution: Fixed Fix Version/s: java-chassis-1.0.0-m2 > service center starter for spring boot/cloud

[jira] [Updated] (SCB-523) maven-remote-resource-plugin execute very slow

[ https://issues.apache.org/jira/browse/SCB-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-523: --- Fix Version/s: java-chassis-1.0.0-m2 > maven-remote-resource-plugin execute very slow >

[jira] [Resolved] (SCB-523) maven-remote-resource-plugin execute very slow

[ https://issues.apache.org/jira/browse/SCB-523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-523. Resolution: Fixed > maven-remote-resource-plugin execute very slow > -- >

[jira] [Commented] (SCB-526) When creating dynamic configuration, we need to fetch once for the configuration when startup

[ https://issues.apache.org/jira/browse/SCB-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456026#comment-16456026 ] liubao commented on SCB-526: Test case: I use demos in

[jira] [Commented] (SCB-526) When creating dynamic configuration, we need to fetch once for the configuration when startup

[ https://issues.apache.org/jira/browse/SCB-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16456038#comment-16456038 ] liubao commented on SCB-526: In order to do this, need to change ConfigUtil to install configurations first and

[jira] [Created] (SCB-574) Using batch API to register schema to improve performance

liubao created SCB-574: -- Summary: Using batch API to register schema to improve performance Key: SCB-574 URL: https://issues.apache.org/jira/browse/SCB-574 Project: Apache ServiceComb Issue Type:

[jira] [Created] (SCB-594) Create a document description for https://github.com/apache/incubator-servicecomb-java-chassis/pull/704

liubao created SCB-594: -- Summary: Create a document description for https://github.com/apache/incubator-servicecomb-java-chassis/pull/704 Key: SCB-594 URL: https://issues.apache.org/jira/browse/SCB-594 Project:

[jira] [Created] (SCB-585) Add ServiceComb-java-chassis reference guide to project

liubao created SCB-585: -- Summary: Add ServiceComb-java-chassis reference guide to project Key: SCB-585 URL: https://issues.apache.org/jira/browse/SCB-585 Project: Apache ServiceComb Issue Type:

[jira] [Resolved] (SCB-526) When creating dynamic configuration, we need to fetch once for the configuration when startup

[ https://issues.apache.org/jira/browse/SCB-526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-526. Resolution: Fixed Fix Version/s: java-chassis-1.0.0-m2 > When creating dynamic configuration, we need to fetch

[jira] [Created] (SCB-582) Provide a way to protection for instance removal

liubao created SCB-582: -- Summary: Provide a way to protection for instance removal Key: SCB-582 URL: https://issues.apache.org/jira/browse/SCB-582 Project: Apache ServiceComb Issue Type: New Feature

[jira] [Commented] (SCB-409) Clean up the Spring Starter

[ https://issues.apache.org/jira/browse/SCB-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483384#comment-16483384 ] liubao commented on SCB-409:

[jira] [Updated] (SCB-425) Add an easier way to read configurations

[ https://issues.apache.org/jira/browse/SCB-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-425: --- Fix Version/s: (was: java-chassis-1.0.0-m2) > Add an easier way to read configurations >

[jira] [Closed] (SCB-582) Provide a way to protection for instance removal

[ https://issues.apache.org/jira/browse/SCB-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao closed SCB-582. -- Resolution: Fixed > Provide a way to protection for instance removal > >

[jira] [Created] (SCB-601) ServiceComb integrated to spring boot or tomcat will print too many logs

liubao created SCB-601: -- Summary: ServiceComb integrated to spring boot or tomcat will print too many logs Key: SCB-601 URL: https://issues.apache.org/jira/browse/SCB-601 Project: Apache ServiceComb

[jira] [Created] (SCB-611) Provide a default Edge service dispatcher to make developer edge easy

liubao created SCB-611: -- Summary: Provide a default Edge service dispatcher to make developer edge easy Key: SCB-611 URL: https://issues.apache.org/jira/browse/SCB-611 Project: Apache ServiceComb

[jira] [Created] (SCB-661) Logs improvement to give better information

liubao created SCB-661: -- Summary: Logs improvement to give better information Key: SCB-661 URL: https://issues.apache.org/jira/browse/SCB-661 Project: Apache ServiceComb Issue Type: Improvement

[jira] [Updated] (SCB-574) Using batch API to register schema to improve performance

[ https://issues.apache.org/jira/browse/SCB-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-574: --- Fix Version/s: (was: Java-chassis-1.0.0) > Using batch API to register schema to improve performance >

[jira] [Created] (SCB-653) When provider returns Transfer-Encoding header and Edge will cause problem

liubao created SCB-653: -- Summary: When provider returns Transfer-Encoding header and Edge will cause problem Key: SCB-653 URL: https://issues.apache.org/jira/browse/SCB-653 Project: Apache ServiceComb

[jira] [Assigned] (SCB-671) Duplicate cse.xxx to servicecomb.xxx to work better in future

[ https://issues.apache.org/jira/browse/SCB-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao reassigned SCB-671: -- Assignee: liubao > Duplicate cse.xxx to servicecomb.xxx to work better in future >

[jira] [Commented] (SCB-490) Service Center verrsion is not forward compatible and needs to be noted in releasenote.

[ https://issues.apache.org/jira/browse/SCB-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16512380#comment-16512380 ] liubao commented on SCB-490: For each SDK release, we should notice the minimal supported SC version. I think

[jira] [Created] (SCB-662) Using cse/servicecomb duplicate key will get list of values

liubao created SCB-662: -- Summary: Using cse/servicecomb duplicate key will get list of values Key: SCB-662 URL: https://issues.apache.org/jira/browse/SCB-662 Project: Apache ServiceComb Issue Type:

[jira] [Created] (SCB-656) When provider returns non 200 code Edge Service will all convert to 502

liubao created SCB-656: -- Summary: When provider returns non 200 code Edge Service will all convert to 502 Key: SCB-656 URL: https://issues.apache.org/jira/browse/SCB-656 Project: Apache ServiceComb

[jira] [Closed] (SCB-656) When provider returns non 200 code Edge Service will all convert to 502

[ https://issues.apache.org/jira/browse/SCB-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao closed SCB-656. -- Resolution: Fixed > When provider returns non 200 code Edge Service will all convert to 502 >

[jira] [Closed] (SCB-653) When provider returns Transfer-Encoding header and Edge will cause problem

[ https://issues.apache.org/jira/browse/SCB-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao closed SCB-653. -- Resolution: Fixed > When provider returns Transfer-Encoding header and Edge will cause problem >

[jira] [Created] (SCB-640) Add black/white list support based on public key handler

liubao created SCB-640: -- Summary: Add black/white list support based on public key handler Key: SCB-640 URL: https://issues.apache.org/jira/browse/SCB-640 Project: Apache ServiceComb Issue Type: New

[jira] [Commented] (SCB-471) vertx upgrade causes use config center push mode error

[ https://issues.apache.org/jira/browse/SCB-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16499702#comment-16499702 ] liubao commented on SCB-471: 2018-06-04 11:13:27,696 [ntloop-thread-0] ERROR ContextImpl - Unhandled exception

[jira] [Reopened] (SCB-471) vertx upgrade causes use config center push mode error

[ https://issues.apache.org/jira/browse/SCB-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao reopened SCB-471: > vertx upgrade causes use config center push mode error > --- > >

[jira] [Assigned] (SCB-471) vertx upgrade causes use config center push mode error

[ https://issues.apache.org/jira/browse/SCB-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao reassigned SCB-471: -- Assignee: liubao (was: laijianbin) > vertx upgrade causes use config center push mode error >

[jira] [Resolved] (SCB-471) vertx upgrade causes use config center push mode error

[ https://issues.apache.org/jira/browse/SCB-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-471. Resolution: Fixed > vertx upgrade causes use config center push mode error >

[jira] [Closed] (SCB-471) vertx upgrade causes use config center push mode error

[ https://issues.apache.org/jira/browse/SCB-471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao closed SCB-471. -- > vertx upgrade causes use config center push mode error > --- > >

[jira] [Updated] (SCB-585) Add ServiceComb-java-chassis reference guide to project

[ https://issues.apache.org/jira/browse/SCB-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-585: --- Fix Version/s: java-chassis-1.0.0-m2 > Add ServiceComb-java-chassis reference guide to project >

[jira] [Resolved] (SCB-585) Add ServiceComb-java-chassis reference guide to project

[ https://issues.apache.org/jira/browse/SCB-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-585. Resolution: Fixed > Add ServiceComb-java-chassis reference guide to project >

[jira] [Closed] (SCB-585) Add ServiceComb-java-chassis reference guide to project

[ https://issues.apache.org/jira/browse/SCB-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao closed SCB-585. -- > Add ServiceComb-java-chassis reference guide to project > --- > >

[jira] [Updated] (SCB-207) Fix known defects related to SCB-184

[ https://issues.apache.org/jira/browse/SCB-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-207: --- Fix Version/s: (was: java-chassis-1.0.0-m2) > Fix known defects related to SCB-184 >

[jira] [Updated] (SCB-696) [AccessLog] If nginx send requests via short-lived connections, %v will print "0.0.0.0"

[ https://issues.apache.org/jira/browse/SCB-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-696: --- Fix Version/s: Java-chassis-1.0.0 > [AccessLog] If nginx send requests via short-lived connections, %v will print >

[jira] [Updated] (SCB-699) 使用Mock机制启动服务中心的时候，报找不到服务的schema定义

[ https://issues.apache.org/jira/browse/SCB-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-699: --- Fix Version/s: Java-chassis-1.0.0 > 使用Mock机制启动服务中心的时候，报找不到服务的schema定义 > - > >

[jira] [Resolved] (SCB-699) 使用Mock机制启动服务中心的时候，报找不到服务的schema定义

[ https://issues.apache.org/jira/browse/SCB-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-699. Resolution: Fixed > 使用Mock机制启动服务中心的时候，报找不到服务的schema定义 > - > > Key:

[jira] [Updated] (SCB-702) Deleted unwanted json-lib maven dependency for foundation-config

[ https://issues.apache.org/jira/browse/SCB-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-702: --- Fix Version/s: (was: java-chassis-1.0.0-m2) Java-chassis-1.0.0 > Deleted unwanted json-lib maven

[jira] [Resolved] (SCB-490) Service Center verrsion is not forward compatible and needs to be noted in releasenote.

[ https://issues.apache.org/jira/browse/SCB-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-490. Resolution: Fixed Fix Version/s: (was: service-center-1.0.0) (was:

[jira] [Closed] (SCB-490) Service Center verrsion is not forward compatible and needs to be noted in releasenote.

[ https://issues.apache.org/jira/browse/SCB-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao closed SCB-490. -- > Service Center verrsion is not forward compatible and needs to be noted in > releasenote. >

[jira] [Commented] (SCB-490) Service Center verrsion is not forward compatible and needs to be noted in releasenote.

[ https://issues.apache.org/jira/browse/SCB-490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528534#comment-16528534 ] liubao commented on SCB-490: Notices in release notes and added match matrics > Service Center verrsion is not

[jira] [Resolved] (SCB-693) registry microservice failed if get host address failed

[ https://issues.apache.org/jira/browse/SCB-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-693. Resolution: Fixed > registry microservice failed if get host address failed >

[jira] [Updated] (SCB-693) registry microservice failed if get host address failed

[ https://issues.apache.org/jira/browse/SCB-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-693: --- Fix Version/s: Java-chassis-1.0.0 > registry microservice failed if get host address failed >

[jira] [Resolved] (SCB-702) Deleted unwanted json-lib maven dependency for foundation-config

[ https://issues.apache.org/jira/browse/SCB-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-702. Resolution: Fixed > Deleted unwanted json-lib maven dependency for foundation-config >

[jira] [Resolved] (SCB-696) [AccessLog] If nginx send requests via short-lived connections, %v will print "0.0.0.0"

[ https://issues.apache.org/jira/browse/SCB-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-696. Resolution: Fixed > [AccessLog] If nginx send requests via short-lived connections, %v will print > "0.0.0.0" >

[jira] [Closed] (SCB-684) Following swagger conventions

[ https://issues.apache.org/jira/browse/SCB-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao closed SCB-684. -- > Following swagger conventions > - > > Key: SCB-684 > URL:

[jira] [Updated] (SCB-685) Service comb chassis must support default values

[ https://issues.apache.org/jira/browse/SCB-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-685: --- Fix Version/s: Java-chassis-1.0.0 > Service comb chassis must support default values >

[jira] [Resolved] (SCB-684) Following swagger conventions

[ https://issues.apache.org/jira/browse/SCB-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-684. Resolution: Fixed Only test cases and comments are given. no code change. > Following swagger conventions >

[jira] [Resolved] (SCB-685) Service comb chassis must support default values

[ https://issues.apache.org/jira/browse/SCB-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-685. Resolution: Fixed Spring MVC fixed. Please create new issue for JAX-RS > Service comb chassis must support default

[jira] [Closed] (SCB-685) Service comb chassis must support default values

[ https://issues.apache.org/jira/browse/SCB-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao closed SCB-685. -- > Service comb chassis must support default values > > >

[jira] [Created] (SCB-700) Check server status when choose an available server

liubao created SCB-700: -- Summary: Check server status when choose an available server Key: SCB-700 URL: https://issues.apache.org/jira/browse/SCB-700 Project: Apache ServiceComb Issue Type: Improvement

[jira] [Reopened] (SCB-697) Service comb chassis must support JAX-RS @DefaultValue

[ https://issues.apache.org/jira/browse/SCB-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao reopened SCB-697: > Service comb chassis must support JAX-RS @DefaultValue > -- > >

[jira] [Resolved] (SCB-697) Service comb chassis must support JAX-RS @DefaultValue

[ https://issues.apache.org/jira/browse/SCB-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-697. Resolution: Fixed > Service comb chassis must support JAX-RS @DefaultValue >

[jira] [Updated] (SCB-697) Service comb chassis must support JAX-RS @DefaultValue

[ https://issues.apache.org/jira/browse/SCB-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-697: --- Fix Version/s: Java-chassis-1.0.0 > Service comb chassis must support JAX-RS @DefaultValue >

[jira] [Closed] (SCB-697) Service comb chassis must support JAX-RS @DefaultValue

[ https://issues.apache.org/jira/browse/SCB-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao closed SCB-697. -- > Service comb chassis must support JAX-RS @DefaultValue > -- > >

[jira] [Resolved] (SCB-703) When consumer invoke void type method in RPC style, an exception is thrown

[ https://issues.apache.org/jira/browse/SCB-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-703. Resolution: Fixed > When consumer invoke void type method in RPC style, an exception is thrown >

[jira] [Resolved] (SCB-705) When consumer invoke an unregistered provider, it will never find this provider even the provider is registered later

[ https://issues.apache.org/jira/browse/SCB-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-705. Resolution: Fixed Fix Version/s: java-chassis-1.0.0 > When consumer invoke an unregistered provider, it will

[jira] [Resolved] (SCB-671) Duplicate cse.xxx to servicecomb.xxx to work better in future

[ https://issues.apache.org/jira/browse/SCB-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-671. Resolution: Fixed > Duplicate cse.xxx to servicecomb.xxx to work better in future >

[jira] [Resolved] (SCB-701) RequestBody(required = false) and when requestBody is null then exception observed

[ https://issues.apache.org/jira/browse/SCB-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-701. Resolution: Fixed Fix Version/s: (was: java-chassis-1.0.0-m2) java-chassis-1.0.0

[jira] [Created] (SCB-709) Implement JAX-RS body parameter required feature

liubao created SCB-709: -- Summary: Implement JAX-RS body parameter required feature Key: SCB-709 URL: https://issues.apache.org/jira/browse/SCB-709 Project: Apache ServiceComb Issue Type: New Feature

[jira] [Created] (SCB-712) Do not register service path to service center when not necessary

liubao created SCB-712: -- Summary: Do not register service path to service center when not necessary Key: SCB-712 URL: https://issues.apache.org/jira/browse/SCB-712 Project: Apache ServiceComb Issue

[jira] [Created] (SCB-711) HTTP2 and other client should be lasy initialized

liubao created SCB-711: -- Summary: HTTP2 and other client should be lasy initialized Key: SCB-711 URL: https://issues.apache.org/jira/browse/SCB-711 Project: Apache ServiceComb Issue Type: Improvement

[jira] [Created] (SCB-523) maven-remote-resource-plugin execute very slow

liubao created SCB-523: -- Summary: maven-remote-resource-plugin execute very slow Key: SCB-523 URL: https://issues.apache.org/jira/browse/SCB-523 Project: Apache ServiceComb Issue Type: Improvement

[jira] [Created] (SCB-165) Service registry not given proper instances

liubao created SCB-165: -- Summary: Service registry not given proper instances Key: SCB-165 URL: https://issues.apache.org/jira/browse/SCB-165 Project: Apache ServiceComb Issue Type: Bug

[jira] [Commented] (SCB-184) Provide starters for Spring Cloud to using service-center and config-center

[ https://issues.apache.org/jira/browse/SCB-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16313275#comment-16313275 ] liubao commented on SCB-184: Demos are given at

[jira] [Created] (SCB-207) Fix known defects related to SCB-184

liubao created SCB-207: -- Summary: Fix known defects related to SCB-184 Key: SCB-207 URL: https://issues.apache.org/jira/browse/SCB-207 Project: Apache ServiceComb Issue Type: Improvement

[jira] [Commented] (SCB-294) when send a request to a not exist microservice, edge will always try to find instances of it.

[ https://issues.apache.org/jira/browse/SCB-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16355003#comment-16355003 ] liubao commented on SCB-294: 测试用例： 场景1： 服务没启动，客户端开始调用；服务启动后，能够调用成功。 场景2: 在通过edge访问的情况：服务没启动->启动。 > when send a

[jira] [Created] (SCB-684) Following swagger conventions

liubao created SCB-684: -- Summary: Following swagger conventions Key: SCB-684 URL: https://issues.apache.org/jira/browse/SCB-684 Project: Apache ServiceComb Issue Type: Improvement Components:

[jira] [Closed] (SCB-661) Logs improvement to give better information

[ https://issues.apache.org/jira/browse/SCB-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao closed SCB-661. -- > Logs improvement to give better information > --- > > Key: SCB-661

[jira] [Resolved] (SCB-661) Logs improvement to give better information

[ https://issues.apache.org/jira/browse/SCB-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-661. Resolution: Fixed Fix Version/s: Java-chassis-1.0.0 > Logs improvement to give better information >

[jira] [Updated] (SCB-483) springmvc over transport rest vertx support file download

[ https://issues.apache.org/jira/browse/SCB-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-483: --- Fix Version/s: java-chassis-1.0.0-m2 > springmvc over transport rest vertx support file download >

[jira] [Updated] (SCB-478) revert netty's version to 4.1.17 and vertx's version to 3.5.0

[ https://issues.apache.org/jira/browse/SCB-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-478: --- Fix Version/s: java-chassis-1.0.0-m2 > revert netty's version to 4.1.17 and vertx's version to 3.5.0 >

[jira] [Reopened] (SCB-285) consumer cache schemas

[ https://issues.apache.org/jira/browse/SCB-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao reopened SCB-285: > consumer cache schemas > -- > > Key: SCB-285 > URL:

[jira] [Updated] (SCB-345) As a developer, i want to use the openssl engine instead of jdk ssl engine to improve ssl/tls performance, so that java chassis has to support config

[ https://issues.apache.org/jira/browse/SCB-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-345: --- Fix Version/s: java-chassis-1.0.0-m2 > As a developer, i want to use the openssl engine instead of jdk ssl engine to >

[jira] [Updated] (SCB-679) Support Cross-Origin Resource Sharing (CORS)

[ https://issues.apache.org/jira/browse/SCB-679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-679: --- Fix Version/s: Java-chassis-1.0.0 > Support Cross-Origin Resource Sharing (CORS) >

[jira] [Updated] (SCB-651) QPS rate limit bug

[ https://issues.apache.org/jira/browse/SCB-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-651: --- Fix Version/s: java-chassis-1.0.0-m2 > QPS rate limit bug > -- > > Key: SCB-651 >

[jira] [Updated] (SCB-509) Update jackson's version to 2.9.5

[ https://issues.apache.org/jira/browse/SCB-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-509: --- Fix Version/s: java-chassis-1.0.0-m2 > Update jackson's version to 2.9.5 > - > >

[jira] [Closed] (SCB-285) consumer cache schemas

[ https://issues.apache.org/jira/browse/SCB-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao closed SCB-285. -- Resolution: Fixed > consumer cache schemas > -- > > Key: SCB-285 >

[jira] [Updated] (SCB-285) consumer cache schemas

[ https://issues.apache.org/jira/browse/SCB-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-285: --- Fix Version/s: java-chassis-1.0.0-m2 > consumer cache schemas > -- > > Key: SCB-285

[jira] [Resolved] (SCB-780) sessionstickrule add the judgement of whether lastServer can also be accessed.

[ https://issues.apache.org/jira/browse/SCB-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-780. Resolution: Fixed > sessionstickrule add the judgement of whether lastServer can also be accessed. >

[jira] [Resolved] (SCB-775) support invoke service using raw type like JsonObject

[ https://issues.apache.org/jira/browse/SCB-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-775. Resolution: Fixed Fix Version/s: java-chassis-1.1.0 > support invoke service using raw type like JsonObject >

[jira] [Resolved] (SCB-778) In tomcat, support register swagger base path with container prefix

[ https://issues.apache.org/jira/browse/SCB-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-778. Resolution: Fixed Fix Version/s: java-chassis-1.1.0 > In tomcat, support register swagger base path with

[jira] [Created] (SCB-802) in rollback scenario, old versions meta is used and invocation is fail

liubao created SCB-802: -- Summary: in rollback scenario, old versions meta is used and invocation is fail Key: SCB-802 URL: https://issues.apache.org/jira/browse/SCB-802 Project: Apache ServiceComb

[jira] [Created] (SCB-787) Server States not clean unavailable server

liubao created SCB-787: -- Summary: Server States not clean unavailable server Key: SCB-787 URL: https://issues.apache.org/jira/browse/SCB-787 Project: Apache ServiceComb Issue Type: Bug Affects

[jira] [Closed] (SCB-592) Spring Zuul Tracing Integration Tests CI failed

[ https://issues.apache.org/jira/browse/SCB-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao closed SCB-592. -- Resolution: Won't Fix > Spring Zuul Tracing Integration Tests CI failed > ---

[jira] [Reopened] (SCB-592) Spring Zuul Tracing Integration Tests CI failed

[ https://issues.apache.org/jira/browse/SCB-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao reopened SCB-592: update version > Spring Zuul Tracing Integration Tests CI failed > --- > >

[jira] [Updated] (SCB-592) Spring Zuul Tracing Integration Tests CI failed

[ https://issues.apache.org/jira/browse/SCB-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-592: --- Fix Version/s: (was: java-chassis-1.0.0) > Spring Zuul Tracing Integration Tests CI failed >

[jira] [Reopened] (SCB-629) 通过Zuul网关传递String类型的json参数，不能被正确接收

[ https://issues.apache.org/jira/browse/SCB-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao reopened SCB-629: remove version > 通过Zuul网关传递String类型的json参数，不能被正确接收 > - > > Key: SCB-629

[jira] [Updated] (SCB-629) 通过Zuul网关传递String类型的json参数，不能被正确接收

[ https://issues.apache.org/jira/browse/SCB-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-629: --- Fix Version/s: (was: java-chassis-1.0.0) > 通过Zuul网关传递String类型的json参数，不能被正确接收 > - >

[jira] [Closed] (SCB-629) 通过Zuul网关传递String类型的json参数，不能被正确接收

[ https://issues.apache.org/jira/browse/SCB-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao closed SCB-629. -- Resolution: Won't Fix > 通过Zuul网关传递String类型的json参数，不能被正确接收 > - > > Key:

[jira] [Created] (SCB-778) In tomcat, support register swagger base path with container prefix

liubao created SCB-778: -- Summary: In tomcat, support register swagger base path with container prefix Key: SCB-778 URL: https://issues.apache.org/jira/browse/SCB-778 Project: Apache ServiceComb Issue

[jira] [Created] (SCB-794) Edge invocation do not properly send servlet filter response code

liubao created SCB-794: -- Summary: Edge invocation do not properly send servlet filter response code Key: SCB-794 URL: https://issues.apache.org/jira/browse/SCB-794 Project: Apache ServiceComb Issue

[jira] [Resolved] (SCB-794) Edge invocation do not properly send servlet filter response code

[ https://issues.apache.org/jira/browse/SCB-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao resolved SCB-794. Resolution: Fixed > Edge invocation do not properly send servlet filter response code >

[jira] [Updated] (SCB-794) Edge invocation do not properly send servlet filter response code

[ https://issues.apache.org/jira/browse/SCB-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-794: --- Fix Version/s: java-chassis-1.1.0 > Edge invocation do not properly send servlet filter response code >

[jira] [Updated] (SCB-767) When using Response to return multi-code message, handlers / filters given ClassCaseException

[ https://issues.apache.org/jira/browse/SCB-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-767: --- Component/s: Java-Chassis > When using Response to return multi-code message, handlers / filters given >

[jira] [Updated] (SCB-715) Working in thread that do not have context class loader

[ https://issues.apache.org/jira/browse/SCB-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-715: --- Component/s: Java-Chassis > Working in thread that do not have context class loader >

[jira] [Updated] (SCB-711) HTTP2 and other client should be lasy initialized

[ https://issues.apache.org/jira/browse/SCB-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-711: --- Component/s: Java-Chassis > HTTP2 and other client should be lasy initialized >

[jira] [Updated] (SCB-778) In tomcat, support register swagger base path with container prefix

[ https://issues.apache.org/jira/browse/SCB-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] liubao updated SCB-778: --- Component/s: Java-Chassis > In tomcat, support register swagger base path with container prefix >

  1   2   3   4   5   6   7   8   9   10   >