[jira] [Created] (SCB-1184) upgrade swagger from 1.5.12 to 1.5.22 to support convert swagger to html
wujimin created SCB-1184: Summary: upgrade swagger from 1.5.12 to 1.5.22 to support convert swagger to html Key: SCB-1184 URL: https://issues.apache.org/jira/browse/SCB-1184 Project: Apache ServiceComb Issue Type: Task Components: Java-Chassis Reporter: wujimin Assignee: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1165) filter bridge methods when generate swagger
[
https://issues.apache.org/jira/browse/SCB-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wujimin resolved SCB-1165.
--
Resolution: Done
Assignee: (was: wujimin)
Fix Version/s: java-chassis-1.2.0
PR submit by demonbug.
> filter bridge methods when generate swagger
> ---
>
> Key: SCB-1165
> URL: https://issues.apache.org/jira/browse/SCB-1165
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Java-Chassis
>Reporter: wujimin
>Priority: Major
> Fix For: java-chassis-1.2.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code:java}
> interface Base {
> void test(T input);
> }
> interface Child extends Base {
> void test(String input);
> }
> class Impl implements Child {
> ..
> }{code}
> Impl.class.getMethods() will get two method name "test", one is normal
> method, another is bridge method.
>
> https://github.com/apache/servicecomb-java-chassis/issues/1104
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SCB-1150) improve how to find problem when error happened
[ https://issues.apache.org/jira/browse/SCB-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1150: - Description: when invocation timeout or isolated or other scenes, it's very difficult to find the problem, we must improve related ability we can create projects in "integration test" to build business like: 3rd -> edge -> A -> B, and enhance fault injection to support inject error or timeout on: * consumer handler request * http client filter beforeSendRequest * http server filter afterReceiveRequest * producer handler request * producer business method * producer handler response * http server filter beforeSendResponse * http client filter afterReceiveResponse * consumer handler response that means there are 21 places will inject faults at least. when fault happened in any place, we should be able to find problem from log. this is a big and very important task, feel free to create subtasks, eg: * provide a marker instance by invocation, to log invocation id and traceId by %marker * enhance fault injection * provide a way to view internal status ** discovery tree status ** isolation status ** eventbus subscribers ** .. * when timeout happened, how to find problem * when error happened, how to find problem * when isolation happened, how to find problem * .. was: when invocation timeout or isolated or other scenes, it's very difficult to find the problem, we must improve related ability we can create projects in "integration test" to build business like: 3rd -> edge -> A -> B, and enhance fault injection to support inject error or timeout on: * consumer handler request * http client filter beforeSendRequest * http server filter afterReceiveRequest * producer handler request * producer business method * producer handler response * http server filter beforeSendResponse * http client filter afterReceiveResponse * consumer handler response that means there are 21 places will inject faults at least. when fault happened in any place, we should be able to find problem from log. this is a big and very important task, feel free to create subtasks, eg: * provide a marker instance by invocation, to log invocation id and traceId by %marker * enhance fault injection * provide a way to view discovery tree status * provide a way to view isolation status * when timeout happened, how to find problem * when error happened, how to find problem * when isolation happened, how to find problem * .. > improve how to find problem when error happened > --- > > Key: SCB-1150 > URL: https://issues.apache.org/jira/browse/SCB-1150 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: YaoHaishi >Priority: Major > > when invocation timeout or isolated or other scenes, it's very difficult to > find the problem, we must improve related ability > > we can create projects in "integration test" to build business like: 3rd -> > edge -> A -> B, and enhance fault injection to support inject error or > timeout on: > * consumer handler request > * http client filter beforeSendRequest > * http server filter afterReceiveRequest > * producer handler request > * producer business method > * producer handler response > * http server filter beforeSendResponse > * http client filter afterReceiveResponse > * consumer handler response > that means there are 21 places will inject faults at least. > when fault happened in any place, we should be able to find problem from log. > > this is a big and very important task, feel free to create subtasks, eg: > * provide a marker instance by invocation, to log invocation id and traceId > by %marker > * enhance fault injection > * provide a way to view internal status > ** discovery tree status > ** isolation status > ** eventbus subscribers > ** .. > * when timeout happened, how to find problem > * when error happened, how to find problem > * when isolation happened, how to find problem > * .. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-1165) filter bridge methods when generate swagger
[
https://issues.apache.org/jira/browse/SCB-1165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wujimin reassigned SCB-1165:
Assignee: wujimin
> filter bridge methods when generate swagger
> ---
>
> Key: SCB-1165
> URL: https://issues.apache.org/jira/browse/SCB-1165
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Java-Chassis
>Reporter: wujimin
>Assignee: wujimin
>Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> {code:java}
> interface Base {
> void test(T input);
> }
> interface Child extends Base {
> void test(String input);
> }
> class Impl implements Child {
> ..
> }{code}
> Impl.class.getMethods() will get two method name "test", one is normal
> method, another is bridge method.
>
> https://github.com/apache/servicecomb-java-chassis/issues/1104
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SCB-1192) add "metrics" prefix to slow invocation configuration
wujimin created SCB-1192: Summary: add "metrics" prefix to slow invocation configuration Key: SCB-1192 URL: https://issues.apache.org/jira/browse/SCB-1192 Project: Apache ServiceComb Issue Type: Task Components: Java-Chassis Reporter: wujimin Assignee: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1188) provide a way to view/convert and download schemas
[ https://issues.apache.org/jira/browse/SCB-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1188: - Description: 1.view from instance directly 2.view as swaggger, and can test online 3.view as html 4.download as swagger or html for each schema 5.download all as swagger or html with a zip file remember status between refersh page 1.active node 2.expanded status 2.schema format !image-2019-03-11-02-34-39-543.png! was: 1.view from instance directly 2.view as swaggger, and can test online 3.view as html 4.download as swagger or html for each schema 5.download all as swagger or html with a zip file !image-2019-03-08-08-50-43-574.png! > provide a way to view/convert and download schemas > -- > > Key: SCB-1188 > URL: https://issues.apache.org/jira/browse/SCB-1188 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Attachments: image-2019-03-11-02-34-39-543.png > > > 1.view from instance directly > 2.view as swaggger, and can test online > 3.view as html > 4.download as swagger or html for each schema > 5.download all as swagger or html with a zip file > > remember status between refersh page > 1.active node > 2.expanded status > 2.schema format > > !image-2019-03-11-02-34-39-543.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1188) provide a way to view/convert and download schemas
[ https://issues.apache.org/jira/browse/SCB-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1188: - Attachment: (was: image-2019-03-08-08-50-43-574.png) > provide a way to view/convert and download schemas > -- > > Key: SCB-1188 > URL: https://issues.apache.org/jira/browse/SCB-1188 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Attachments: image-2019-03-11-02-34-39-543.png > > > 1.view from instance directly > 2.view as swaggger, and can test online > 3.view as html > 4.download as swagger or html for each schema > 5.download all as swagger or html with a zip file > > remember status between refersh page > 1.active node > 2.expanded status > 2.schema format > > !image-2019-03-11-02-34-39-543.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1188) provide a way to view/convert and download schemas
[ https://issues.apache.org/jira/browse/SCB-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1188: - Description: 1.view from instance directly 2.view as swaggger, and can test online 3.view as html 4.download as swagger or html for each schema 5.download all as swagger or html with a zip file remember status between refersh page 1.active node 2.expanded status 3.schema format !image-2019-03-11-02-34-39-543.png! was: 1.view from instance directly 2.view as swaggger, and can test online 3.view as html 4.download as swagger or html for each schema 5.download all as swagger or html with a zip file remember status between refersh page 1.active node 2.expanded status 2.schema format !image-2019-03-11-02-34-39-543.png! > provide a way to view/convert and download schemas > -- > > Key: SCB-1188 > URL: https://issues.apache.org/jira/browse/SCB-1188 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Attachments: image-2019-03-11-02-34-39-543.png > > > 1.view from instance directly > 2.view as swaggger, and can test online > 3.view as html > 4.download as swagger or html for each schema > 5.download all as swagger or html with a zip file > > remember status between refersh page > 1.active node > 2.expanded status > 3.schema format > > !image-2019-03-11-02-34-39-543.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1067) serialize/deserialize method parameters and result
[ https://issues.apache.org/jira/browse/SCB-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1067: - Fix Version/s: (was: java-chassis-1.2.0) > serialize/deserialize method parameters and result > -- > > Key: SCB-1067 > URL: https://issues.apache.org/jira/browse/SCB-1067 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-921) check if swagger compatible to protobuf and choose transport automatically
[ https://issues.apache.org/jira/browse/SCB-921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-921: Fix Version/s: (was: java-chassis-1.2.0) > check if swagger compatible to protobuf and choose transport automatically > -- > > Key: SCB-921 > URL: https://issues.apache.org/jira/browse/SCB-921 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > > include these rules at least: > * not support List/List (try to support) > * array in deserialize target model (try to support) > (https://github.com/protocolbuffers/protobuf/issues/3749) > * file upload and download -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1191) NPE When return type is ResponseEntity
[ https://issues.apache.org/jira/browse/SCB-1191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1191. -- Resolution: Fixed Fix Version/s: java-chassis-1.2.0 https://github.com/apache/servicecomb-java-chassis/pull/1124 > NPE When return type is ResponseEntity > > > Key: SCB-1191 > URL: https://issues.apache.org/jira/browse/SCB-1191 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0, java-chassis-1.1.0 >Reporter: Willem Jiang >Priority: Major > Fix For: java-chassis-1.2.0 > > Time Spent: 10m > Remaining Estimate: 0h > > Find the code in OperationGenerator.java like below. If the type of return is > void, it will return null and that is right. But, when the type of return is > ResponseEntity, it will get NPE in the future. > You can find more information here > https://github.com/apache/servicecomb-java-chassis/issues/1122 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1179) Optimize the mainclass auto-discovery logic to cover more scenes.
[ https://issues.apache.org/jira/browse/SCB-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1179. -- Resolution: Done Fix Version/s: java-chassis-1.2.0 > Optimize the mainclass auto-discovery logic to cover more scenes. > - > > Key: SCB-1179 > URL: https://issues.apache.org/jira/browse/SCB-1179 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: yangshaoqin1 >Assignee: yangshaoqin1 >Priority: Major > Fix For: java-chassis-1.2.0 > > Time Spent: 10m > Remaining Estimate: 0h > > In the "mvn spring-boot:repackage" scenario, locate the mainClass by looking > for the "start-class" attribute in the "MANIFEST.MF" file. > In the "mvn spring-boot:run" scenario, look up mainClass through the call > stack. > Record the packages of bean scanned into the log. > Add related unit tests. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-229) support rxJava Observable
[ https://issues.apache.org/jira/browse/SCB-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-229: Fix Version/s: (was: java-chassis-1.2.0) > support rxJava Observable > - > > Key: SCB-229 > URL: https://issues.apache.org/jira/browse/SCB-229 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: Yang Bo >Priority: Major > > just like CompletableFuture -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1178) In the unit test, the issue of assertEquals and Float.MAX_VALUE.
[
https://issues.apache.org/jira/browse/SCB-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wujimin resolved SCB-1178.
--
Resolution: Done
Fix Version/s: java-chassis-1.2.0
> In the unit test, the issue of assertEquals and Float.MAX_VALUE.
>
>
> Key: SCB-1178
> URL: https://issues.apache.org/jira/browse/SCB-1178
> Project: Apache ServiceComb
> Issue Type: Improvement
> Components: Java-Chassis
>Reporter: yangshaoqin1
>Assignee: yangshaoqin1
>Priority: Major
> Fix For: java-chassis-1.2.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> In unit tests, code like the following can pass the test, which means that
> there is an invalid unit test code that needs to be improved.
> {code:java}
> Assert.assertEquals(Float.MAX_VALUE, Float.MAX_VALUE-1,0);
> Assert.assertEquals(Float.MAX_VALUE, Float.MAX_VALUE-10,0);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SCB-1162) document for PriorityProperty/InjectProperties/InjectProperty
[ https://issues.apache.org/jira/browse/SCB-1162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1162. -- Resolution: Done Fix Version/s: java-chassis-1.2.0 > document for PriorityProperty/InjectProperties/InjectProperty > - > > Key: SCB-1162 > URL: https://issues.apache.org/jira/browse/SCB-1162 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: yangshaoqin1 >Priority: Major > Fix For: java-chassis-1.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1188) provide a way to view/convert and download schemas
[ https://issues.apache.org/jira/browse/SCB-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1188. -- Resolution: Done Fix Version/s: java-chassis-1.2.0 > provide a way to view/convert and download schemas > -- > > Key: SCB-1188 > URL: https://issues.apache.org/jira/browse/SCB-1188 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.2.0 > > Attachments: image-2019-03-11-02-34-39-543.png > > Time Spent: 20m > Remaining Estimate: 0h > > 1.view from instance directly > 2.view as swaggger, and can test online > 3.view as html > 4.download as swagger or html for each schema > 5.download all as swagger or html with a zip file > > remember status between refersh page > 1.active node > 2.expanded status > 3.schema format > > !image-2019-03-11-02-34-39-543.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1197) enhance provider tracing handler to inherit spans from http header
wujimin created SCB-1197: Summary: enhance provider tracing handler to inherit spans from http header Key: SCB-1197 URL: https://issues.apache.org/jira/browse/SCB-1197 Project: Apache ServiceComb Issue Type: Task Components: Java-Chassis Reporter: wujimin [https://github.com/apache/servicecomb-java-chassis/issues/1116] currently we already inherit traceId from http header in: org.apache.servicecomb.core.Invocation#initTraceId(org.apache.servicecomb.core.tracing.TraceIdGenerator) to inherit spans from http header we need to change: org.apache.servicecomb.tracing.zipkin.ZipkinProviderDelegate#INVOCATION_STRING_GETTER, (if key is SPAN_ID_HEADER_NAME) # try to get from invocation.context, if already exists then return directly # if invocation.requestEx is no null, try to get from http header # if still can not get spanId, then make spanId equals traceId maybe this is enough, but i'm not sure, need to test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1206) sort schemas in inspector ui
[ https://issues.apache.org/jira/browse/SCB-1206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1206. -- Resolution: Done Fix Version/s: java-chassis-1.2.0 > sort schemas in inspector ui > > > Key: SCB-1206 > URL: https://issues.apache.org/jira/browse/SCB-1206 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1208) improve slow invocation logger: log remote address
[ https://issues.apache.org/jira/browse/SCB-1208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1208. -- Resolution: Done Fix Version/s: java-chassis-1.2.0 > improve slow invocation logger: log remote address > -- > > Key: SCB-1208 > URL: https://issues.apache.org/jira/browse/SCB-1208 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1205) improve edge forward http2 request
wujimin created SCB-1205: Summary: improve edge forward http2 request Key: SCB-1205 URL: https://issues.apache.org/jira/browse/SCB-1205 Project: Apache ServiceComb Issue Type: Task Components: Java-Chassis Reporter: wujimin Assignee: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1205) improve edge forward http2 request
[ https://issues.apache.org/jira/browse/SCB-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1205: - Issue Type: Improvement (was: Task) > improve edge forward http2 request > -- > > Key: SCB-1205 > URL: https://issues.apache.org/jira/browse/SCB-1205 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1206) sort schemas in inspector ui
wujimin created SCB-1206: Summary: sort schemas in inspector ui Key: SCB-1206 URL: https://issues.apache.org/jira/browse/SCB-1206 Project: Apache ServiceComb Issue Type: Improvement Components: Java-Chassis Reporter: wujimin Assignee: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1208) improve slow invocation logger: log remote address
wujimin created SCB-1208: Summary: improve slow invocation logger: log remote address Key: SCB-1208 URL: https://issues.apache.org/jira/browse/SCB-1208 Project: Apache ServiceComb Issue Type: Improvement Components: Java-Chassis Reporter: wujimin Assignee: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1205) improve edge forward http2 request
[ https://issues.apache.org/jira/browse/SCB-1205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1205. -- Resolution: Done Fix Version/s: java-chassis-1.2.0 > improve edge forward http2 request > -- > > Key: SCB-1205 > URL: https://issues.apache.org/jira/browse/SCB-1205 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1192) add "metrics" prefix to slow invocation configuration
[ https://issues.apache.org/jira/browse/SCB-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1192. -- Resolution: Done Fix Version/s: java-chassis-1.2.0 > add "metrics" prefix to slow invocation configuration > -- > > Key: SCB-1192 > URL: https://issues.apache.org/jira/browse/SCB-1192 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1188) provide a way to view/convert and download schemas
wujimin created SCB-1188: Summary: provide a way to view/convert and download schemas Key: SCB-1188 URL: https://issues.apache.org/jira/browse/SCB-1188 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: wujimin Assignee: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1188) provide a way to view/convert and download schemas
[ https://issues.apache.org/jira/browse/SCB-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1188: - Attachment: image-2019-03-08-08-50-43-574.png > provide a way to view/convert and download schemas > -- > > Key: SCB-1188 > URL: https://issues.apache.org/jira/browse/SCB-1188 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Attachments: image-2019-03-08-08-50-43-574.png > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1188) provide a way to view/convert and download schemas
[ https://issues.apache.org/jira/browse/SCB-1188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1188: - Description: 1.view from instance directly 2.view as swaggger, and can test online 3.view as html 4.download as swagger or html for each schema 5.download all as swagger or html with a zip file !image-2019-03-08-08-50-43-574.png! > provide a way to view/convert and download schemas > -- > > Key: SCB-1188 > URL: https://issues.apache.org/jira/browse/SCB-1188 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Attachments: image-2019-03-08-08-50-43-574.png > > > 1.view from instance directly > 2.view as swaggger, and can test online > 3.view as html > 4.download as swagger or html for each schema > 5.download all as swagger or html with a zip file > !image-2019-03-08-08-50-43-574.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1212) change SwaggerConsumer response to not depend on swagger class generation
wujimin created SCB-1212: Summary: change SwaggerConsumer response to not depend on swagger class generation Key: SCB-1212 URL: https://issues.apache.org/jira/browse/SCB-1212 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: wujimin Assignee: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1213) swagger generator not depend on spring
wujimin created SCB-1213: Summary: swagger generator not depend on spring Key: SCB-1213 URL: https://issues.apache.org/jira/browse/SCB-1213 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: wujimin Assignee: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1214) change weak-contract-type branch version to weak-contract-type-SNAPSHOT
wujimin created SCB-1214: Summary: change weak-contract-type branch version to weak-contract-type-SNAPSHOT Key: SCB-1214 URL: https://issues.apache.org/jira/browse/SCB-1214 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: wujimin Assignee: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1214) change weak-contract-type branch version to weak-contract-type-SNAPSHOT
[ https://issues.apache.org/jira/browse/SCB-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1214. -- Resolution: Done Fix Version/s: java-chassis-2.0.0 > change weak-contract-type branch version to weak-contract-type-SNAPSHOT > --- > > Key: SCB-1214 > URL: https://issues.apache.org/jira/browse/SCB-1214 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1157) spring-boot2-starter-discovery and spring-boot-starter-discovery depend on zuul is not correct
[ https://issues.apache.org/jira/browse/SCB-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1157: - Labels: newbie (was: ) > spring-boot2-starter-discovery and spring-boot-starter-discovery depend on > zuul is not correct > -- > > Key: SCB-1157 > URL: https://issues.apache.org/jira/browse/SCB-1157 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: wujimin >Priority: Major > Labels: newbie > > zuul or spring cloud gate depend on discovery is correct -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1157) spring-boot2-starter-discovery and spring-boot-starter-discovery depend on zuul is not correct
wujimin created SCB-1157: Summary: spring-boot2-starter-discovery and spring-boot-starter-discovery depend on zuul is not correct Key: SCB-1157 URL: https://issues.apache.org/jira/browse/SCB-1157 Project: Apache ServiceComb Issue Type: Improvement Components: Java-Chassis Reporter: wujimin zuul or spring cloud gate depend on discovery is correct -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-638) create mechanism for read config item by priority
[
https://issues.apache.org/jira/browse/SCB-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
wujimin resolved SCB-638.
-
Resolution: Done
Fix Version/s: java-chassis-1.2.0
> create mechanism for read config item by priority
> --
>
> Key: SCB-638
> URL: https://issues.apache.org/jira/browse/SCB-638
> Project: Apache ServiceComb
> Issue Type: Task
> Components: Java-Chassis
>Reporter: wujimin
>Assignee: wujimin
>Priority: Major
> Fix For: java-chassis-1.2.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> currently, we have so many config item need to read by priority.
> 1.read operation level
> 2.if operation level not exist, then read schema level
> 3.if schema level not exist, then read microservice level
> 4.if microservice level not exist, then read global level (only for consumer)
>
> everyone repeated the logic, and try all the level for every invocation
> we can provide a mechanism to handle this logic, eg:
>
> {code:java}
> class XxxConfig{
> @Config(prefix="servicecomb.request.time")
> private int timeout;
> ..
> }
> OperationMeta.extData changed from ConcurrentHashMap to ConcurrentHashMapEx
> XxxConfig config = operationMeta.getExtData().computeIfAbsent("...",
> k->ConfigFactory.create(operationMeta));
> config.getTimeout() // this is what we want. all try logic is
> triggered by config change callback, not run for every invocation.{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SCB-1148) read transport configuration from model
[ https://issues.apache.org/jira/browse/SCB-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1148: - Summary: read transport configuration from model (was: consumer request timeout parameter read from OperationConfig) > read transport configuration from model > --- > > Key: SCB-1148 > URL: https://issues.apache.org/jira/browse/SCB-1148 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1150) improve how to find problem when error happened
[ https://issues.apache.org/jira/browse/SCB-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1150: - Description: when invocation timeout or isolated or other scenes, it's very difficult to find the problem, we must improve related ability we can create projects in "integration test" to build business like: 3rd -> edge -> A -> B, and enhance fault injection to support inject error or timeout on: * consumer handler request * http client filter beforeSendRequest * http server filter afterReceiveRequest * producer handler request * producer business method * producer handler response * http server filter beforeSendResponse * http client filter afterReceiveResponse * consumer handler response that means there are 21 places will inject faults. when fault happened in any place, we should be able to find problem from log. this is a big and very important task, feel free to create subtasks, eg: * provide a marker instance by invocation, to log invocation id and traceId by %marker * enhance fault injection * provide a way to view discovery tree status * provide a way to view isolation status * when timeout happened, how to find problem * when error happened, how to find problem * when isolation happened, how to find problem * .. was: when invocation timeout or isolated or other scenes, it's very difficult to find the problem, we must improve related ability we can create projects in "integration test" to build business like: 3rd -> edge -> A -> B, and enhance fault injection to support inject error or timeout on: * consumer handler request * http client filter beforeSendRequest * http server filter afterReceiveRequest * producer handler request * producer business method * producer handler response * http server filter beforeSendResponse * http client filter afterReceiveResponse * consumer handler response that means there are 21 places will inject faults. when fault happened in any place, we should be able to find problem from log. this is a big and very important task, feel free to create subtasks, eg: * create rule for filter or handler, when execute an action caused lost invocation context in threadLocal, it's develop's duty to restore context in threadLocal, that makes we can log invocation id and traceId by MDC mechanism * enhance fault injection * provide a way to view discovery tree status * provide a way to view isolation status * when timeout happened, how to find problem * when error happened, how to find problem * when isolation happened, how to find problem * .. > improve how to find problem when error happened > --- > > Key: SCB-1150 > URL: https://issues.apache.org/jira/browse/SCB-1150 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Priority: Major > > when invocation timeout or isolated or other scenes, it's very difficult to > find the problem, we must improve related ability > > we can create projects in "integration test" to build business like: 3rd -> > edge -> A -> B, and enhance fault injection to support inject error or > timeout on: > * consumer handler request > * http client filter beforeSendRequest > * http server filter afterReceiveRequest > * producer handler request > * producer business method > * producer handler response > * http server filter beforeSendResponse > * http client filter afterReceiveResponse > * consumer handler response > that means there are 21 places will inject faults. > when fault happened in any place, we should be able to find problem from log. > > this is a big and very important task, feel free to create subtasks, eg: > * provide a marker instance by invocation, to log invocation id and traceId > by %marker > * enhance fault injection > * provide a way to view discovery tree status > * provide a way to view isolation status > * when timeout happened, how to find problem > * when error happened, how to find problem > * when isolation happened, how to find problem > * .. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1153) provide traceId-invocationId by marker mechanism
wujimin created SCB-1153: Summary: provide traceId-invocationId by marker mechanism Key: SCB-1153 URL: https://issues.apache.org/jira/browse/SCB-1153 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: wujimin Assignee: wujimin Fix For: java-chassis-1.2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1154) invocation related log must invoke with marker
wujimin created SCB-1154: Summary: invocation related log must invoke with marker Key: SCB-1154 URL: https://issues.apache.org/jira/browse/SCB-1154 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: wujimin LOGGER.info(invocation.getMarker(), ..) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1137) optimize http2 performance
[ https://issues.apache.org/jira/browse/SCB-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1137: - Description: http2 is slower than http1.1 1."get connection" is slower than http1.1,very slow 2.request queued in producer thread pool, maybe there is condition race problem. "pool-5-thread-2" #105 prio=5 os_prio=0 tid=0x7f9be000a000 nid=0x3512 waiting for monitor entry [0x7f9ba01d5000] java.lang.Thread.State: BLOCKED (on object monitor) at io.vertx.core.http.impl.Http2ServerResponseImpl.headers(Http2ServerResponseImpl.java:208) - waiting to lock <0x82024988> (a io.vertx.core.http.impl.Http2ServerConnection) at org.apache.servicecomb.foundation.vertx.http.VertxServerResponseToHttpServletResponse.setContentType(VertxServerResponseToHttpServletResponse.java:51) at org.apache.servicecomb.common.rest.filter.inner.ServerRestArgsFilter.beforeSendResponseAsync(ServerRestArgsFilter.java:79) at org.apache.servicecomb.common.rest.filter.HttpServerFilterBeforeSendResponseExecutor.safeInvoke(HttpServerFilterBeforeSendResponseExecutor.java:52) at org.apache.servicecomb.common.rest.filter.HttpServerFilterBeforeSendResponseExecutor.doRun(HttpServerFilterBeforeSendResponseExecutor.java:74) at org.apache.servicecomb.common.rest.filter.HttpServerFilterBeforeSendResponseExecutor.run(HttpServerFilterBeforeSendResponseExecutor.java:44) at org.apache.servicecomb.common.rest.AbstractRestInvocation.executeHttpServerFilters(AbstractRestInvocation.java:284) at org.apache.servicecomb.common.rest.AbstractRestInvocation.sendResponse(AbstractRestInvocation.java:278) at org.apache.servicecomb.common.rest.AbstractRestInvocation.sendResponseQuietly(AbstractRestInvocation.java:255) at org.apache.servicecomb.common.rest.AbstractRestInvocation.lambda$doInvoke$2(AbstractRestInvocation.java:238) at org.apache.servicecomb.common.rest.AbstractRestInvocation$$Lambda$416/2134056601.handle(Unknown Source) was: http2 is slower than http1.1 1."get connection" is slower than http1.1,very slow 2.request queued in producer thread pool, maybe there is condition race problem. > optimize http2 performance > -- > > Key: SCB-1137 > URL: https://issues.apache.org/jira/browse/SCB-1137 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > > http2 is slower than http1.1 > 1."get connection" is slower than http1.1,very slow > 2.request queued in producer thread pool, maybe there is condition race > problem. > > "pool-5-thread-2" #105 prio=5 os_prio=0 tid=0x7f9be000a000 nid=0x3512 > waiting for monitor entry [0x7f9ba01d5000] > java.lang.Thread.State: BLOCKED (on object monitor) > at > io.vertx.core.http.impl.Http2ServerResponseImpl.headers(Http2ServerResponseImpl.java:208) > - waiting to lock <0x82024988> (a > io.vertx.core.http.impl.Http2ServerConnection) > at > org.apache.servicecomb.foundation.vertx.http.VertxServerResponseToHttpServletResponse.setContentType(VertxServerResponseToHttpServletResponse.java:51) > at > org.apache.servicecomb.common.rest.filter.inner.ServerRestArgsFilter.beforeSendResponseAsync(ServerRestArgsFilter.java:79) > at > org.apache.servicecomb.common.rest.filter.HttpServerFilterBeforeSendResponseExecutor.safeInvoke(HttpServerFilterBeforeSendResponseExecutor.java:52) > at > org.apache.servicecomb.common.rest.filter.HttpServerFilterBeforeSendResponseExecutor.doRun(HttpServerFilterBeforeSendResponseExecutor.java:74) > at > org.apache.servicecomb.common.rest.filter.HttpServerFilterBeforeSendResponseExecutor.run(HttpServerFilterBeforeSendResponseExecutor.java:44) > at > org.apache.servicecomb.common.rest.AbstractRestInvocation.executeHttpServerFilters(AbstractRestInvocation.java:284) > at > org.apache.servicecomb.common.rest.AbstractRestInvocation.sendResponse(AbstractRestInvocation.java:278) > at > org.apache.servicecomb.common.rest.AbstractRestInvocation.sendResponseQuietly(AbstractRestInvocation.java:255) > at > org.apache.servicecomb.common.rest.AbstractRestInvocation.lambda$doInvoke$2(AbstractRestInvocation.java:238) > at > org.apache.servicecomb.common.rest.AbstractRestInvocation$$Lambda$416/2134056601.handle(Unknown > Source) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1156) avoid collect wrong invocation stage data when rest invoke failed
wujimin created SCB-1156: Summary: avoid collect wrong invocation stage data when rest invoke failed Key: SCB-1156 URL: https://issues.apache.org/jira/browse/SCB-1156 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Reporter: wujimin Assignee: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1150) improve how to find problem when error happened
wujimin created SCB-1150: Summary: improve how to find problem when error happened Key: SCB-1150 URL: https://issues.apache.org/jira/browse/SCB-1150 Project: Apache ServiceComb Issue Type: Task Components: Java-Chassis Reporter: wujimin when invocation timeout or isolated or other scenes, it's very difficult to find the problem, we must improve related ability we can create projects in "integration test" to build business like: 3rd -> edge -> A -> B, and enhance fault injection to support inject error or timeout on: * consumer handler request * http client filter beforeSendRequest * http server filter afterReceiveRequest * producer handler request * producer business method * producer handler response * http server filter beforeSendResponse * http client filter afterReceiveResponse * consumer handler response that means there are 21 places will inject faults. when fault happened in any place, we should be able to find problem from log. this is a big and very important task, feel free to create subtasks, eg: * create rule for filter or handler, when execute an action caused lost invocation context in threadLocal, it's develop's duty to restore context in threadLocal, that makes we can log invocation id and traceId by MDC mechanism * enhance fault injection * provide a way to view discovery tree status * provide a way to view isolation status * when timeout happened, how to find problem * when error happened, how to find problem * when isolation happened, how to find problem * .. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1146) update PR template
wujimin created SCB-1146: Summary: update PR template Key: SCB-1146 URL: https://issues.apache.org/jira/browse/SCB-1146 Project: Apache ServiceComb Issue Type: Improvement Components: Java-Chassis Reporter: wujimin Assignee: wujimin Fix For: java-chassis-1.2.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1147) log invocation stage trace information if too slow
[ https://issues.apache.org/jira/browse/SCB-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1147: - Summary: log invocation stage trace information if too slow (was: log all invocation stage trace information if too slow) > log invocation stage trace information if too slow > -- > > Key: SCB-1147 > URL: https://issues.apache.org/jira/browse/SCB-1147 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1147) log all invocation stage trace information if too slow
wujimin created SCB-1147: Summary: log all invocation stage trace information if too slow Key: SCB-1147 URL: https://issues.apache.org/jira/browse/SCB-1147 Project: Apache ServiceComb Issue Type: Task Components: Java-Chassis Reporter: wujimin Assignee: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1146) update PR template
[ https://issues.apache.org/jira/browse/SCB-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1146. -- Resolution: Done > update PR template > -- > > Key: SCB-1146 > URL: https://issues.apache.org/jira/browse/SCB-1146 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1148) consumer request timeout parameter read from OperationConfig
wujimin created SCB-1148: Summary: consumer request timeout parameter read from OperationConfig Key: SCB-1148 URL: https://issues.apache.org/jira/browse/SCB-1148 Project: Apache ServiceComb Issue Type: Task Components: Java-Chassis Reporter: wujimin Assignee: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1141) latest versionRule can not update to new version
[ https://issues.apache.org/jira/browse/SCB-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1141. -- Resolution: Fixed Fix Version/s: java-chassis-1.2.0 > latest versionRule can not update to new version > > > Key: SCB-1141 > URL: https://issues.apache.org/jira/browse/SCB-1141 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.2.0 > > Time Spent: 40m > Remaining Estimate: 0h > > 1.consumer set versionRule to latest > 2.producer version is 1.0.0 > 3.consumer not reboot and some instances of producer upgrade to 1.1.0 > consumer pulled both instances of 1.0.0 and 1.1.0 > consumer abandoned 1.1.0, retaining 1.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1147) log invocation stage trace information if too slow
[ https://issues.apache.org/jira/browse/SCB-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1147. -- Resolution: Done Fix Version/s: java-chassis-1.2.0 > log invocation stage trace information if too slow > -- > > Key: SCB-1147 > URL: https://issues.apache.org/jira/browse/SCB-1147 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1150) improve how to find problem when error happened
[ https://issues.apache.org/jira/browse/SCB-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1150: - Description: when invocation timeout or isolated or other scenes, it's very difficult to find the problem, we must improve related ability we can create projects in "integration test" to build business like: 3rd -> edge -> A -> B, and enhance fault injection to support inject error or timeout on: * consumer handler request * http client filter beforeSendRequest * http server filter afterReceiveRequest * producer handler request * producer business method * producer handler response * http server filter beforeSendResponse * http client filter afterReceiveResponse * consumer handler response that means there are 21 places will inject faults at least. when fault happened in any place, we should be able to find problem from log. this is a big and very important task, feel free to create subtasks, eg: * provide a marker instance by invocation, to log invocation id and traceId by %marker * enhance fault injection * provide a way to view discovery tree status * provide a way to view isolation status * when timeout happened, how to find problem * when error happened, how to find problem * when isolation happened, how to find problem * .. was: when invocation timeout or isolated or other scenes, it's very difficult to find the problem, we must improve related ability we can create projects in "integration test" to build business like: 3rd -> edge -> A -> B, and enhance fault injection to support inject error or timeout on: * consumer handler request * http client filter beforeSendRequest * http server filter afterReceiveRequest * producer handler request * producer business method * producer handler response * http server filter beforeSendResponse * http client filter afterReceiveResponse * consumer handler response that means there are 21 places will inject faults. when fault happened in any place, we should be able to find problem from log. this is a big and very important task, feel free to create subtasks, eg: * provide a marker instance by invocation, to log invocation id and traceId by %marker * enhance fault injection * provide a way to view discovery tree status * provide a way to view isolation status * when timeout happened, how to find problem * when error happened, how to find problem * when isolation happened, how to find problem * .. > improve how to find problem when error happened > --- > > Key: SCB-1150 > URL: https://issues.apache.org/jira/browse/SCB-1150 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: YaoHaishi >Priority: Major > > when invocation timeout or isolated or other scenes, it's very difficult to > find the problem, we must improve related ability > > we can create projects in "integration test" to build business like: 3rd -> > edge -> A -> B, and enhance fault injection to support inject error or > timeout on: > * consumer handler request > * http client filter beforeSendRequest > * http server filter afterReceiveRequest > * producer handler request > * producer business method > * producer handler response > * http server filter beforeSendResponse > * http client filter afterReceiveResponse > * consumer handler response > that means there are 21 places will inject faults at least. > when fault happened in any place, we should be able to find problem from log. > > this is a big and very important task, feel free to create subtasks, eg: > * provide a marker instance by invocation, to log invocation id and traceId > by %marker > * enhance fault injection > * provide a way to view discovery tree status > * provide a way to view isolation status > * when timeout happened, how to find problem > * when error happened, how to find problem > * when isolation happened, how to find problem > * .. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-1150) improve how to find problem when error happened
[ https://issues.apache.org/jira/browse/SCB-1150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin reassigned SCB-1150: Assignee: YaoHaishi > improve how to find problem when error happened > --- > > Key: SCB-1150 > URL: https://issues.apache.org/jira/browse/SCB-1150 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: YaoHaishi >Priority: Major > > when invocation timeout or isolated or other scenes, it's very difficult to > find the problem, we must improve related ability > > we can create projects in "integration test" to build business like: 3rd -> > edge -> A -> B, and enhance fault injection to support inject error or > timeout on: > * consumer handler request > * http client filter beforeSendRequest > * http server filter afterReceiveRequest > * producer handler request > * producer business method > * producer handler response > * http server filter beforeSendResponse > * http client filter afterReceiveResponse > * consumer handler response > that means there are 21 places will inject faults. > when fault happened in any place, we should be able to find problem from log. > > this is a big and very important task, feel free to create subtasks, eg: > * provide a marker instance by invocation, to log invocation id and traceId > by %marker > * enhance fault injection > * provide a way to view discovery tree status > * provide a way to view isolation status > * when timeout happened, how to find problem > * when error happened, how to find problem > * when isolation happened, how to find problem > * .. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-1157) spring-boot2-starter-discovery and spring-boot-starter-discovery depend on zuul is not correct
[ https://issues.apache.org/jira/browse/SCB-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin reassigned SCB-1157: Assignee: yangshaoqin1 > spring-boot2-starter-discovery and spring-boot-starter-discovery depend on > zuul is not correct > -- > > Key: SCB-1157 > URL: https://issues.apache.org/jira/browse/SCB-1157 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: wujimin >Assignee: yangshaoqin1 >Priority: Major > Labels: newbie > > zuul or spring cloud gate depend on discovery is correct -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1136) change default settings of sync executor
[ https://issues.apache.org/jira/browse/SCB-1136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1136. -- Resolution: Done Fix Version/s: java-chassis-1.2.0 > change default settings of sync executor > > > Key: SCB-1136 > URL: https://issues.apache.org/jira/browse/SCB-1136 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > currently we provide a default sync invocation executor: > * default integrate two fixed thread pool > * thread count for one pool is equals cpu countfor most customers, thread > count of one pool is too small, and fixed thread pool is not so good, so will > change to: > * default integrate two ThreadPoolExecutor > * support to configure core/max thread count, keepAlive time and max queue > size for one pool > * default core thread: 25, same to tomcat > * default max thread: 100, tomcat is 200, because we have 2 pool, so change > to 100 > * default keepAlive: 1 minute, same to tomcat > * default max queue size: Integer.MAX_VALUE, same to tomcat > or default integrate only one ThreadPoolExecutor? > because most customers TPS is not so high, no need to do this optimize -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1141) latest versionRule can not update to new version
wujimin created SCB-1141: Summary: latest versionRule can not update to new version Key: SCB-1141 URL: https://issues.apache.org/jira/browse/SCB-1141 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Reporter: wujimin Assignee: wujimin 1.consumer set versionRule to latest 2.producer version is 1.0.0 2.consumer not reboot and some instances of producer upgrade to 1.1.0 consumer pulled both instances of 1.0.0 and 1.1.0 consumer abandoned 1.1.0, retaining 1.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1141) latest versionRule can not update to new version
[ https://issues.apache.org/jira/browse/SCB-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1141: - Description: 1.consumer set versionRule to latest 2.producer version is 1.0.0 3.consumer not reboot and some instances of producer upgrade to 1.1.0 consumer pulled both instances of 1.0.0 and 1.1.0 consumer abandoned 1.1.0, retaining 1.0.0 was: 1.consumer set versionRule to latest 2.producer version is 1.0.0 2.consumer not reboot and some instances of producer upgrade to 1.1.0 consumer pulled both instances of 1.0.0 and 1.1.0 consumer abandoned 1.1.0, retaining 1.0.0 > latest versionRule can not update to new version > > > Key: SCB-1141 > URL: https://issues.apache.org/jira/browse/SCB-1141 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > 1.consumer set versionRule to latest > 2.producer version is 1.0.0 > 3.consumer not reboot and some instances of producer upgrade to 1.1.0 > consumer pulled both instances of 1.0.0 and 1.1.0 > consumer abandoned 1.1.0, retaining 1.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1136) change default settings of sync executor
wujimin created SCB-1136: Summary: change default settings of sync executor Key: SCB-1136 URL: https://issues.apache.org/jira/browse/SCB-1136 Project: Apache ServiceComb Issue Type: Task Components: Java-Chassis Reporter: wujimin currently we provide a default sync invocation executor: * default integrate two fixed thread pool * thread count for one pool is equals cpu countfor most customers, thread count of one pool is too small, and fixed thread pool is not so good, so will change to: * default integrate two ThreadPoolExecutor * support to configure core/max thread count, keepAlive time and max queue size for one pool * default core thread: 25, same to tomcat * default max thread: 100, tomcat is 200, because we have 2 pool, so change to 100 * default keepAlive: 1 minute, same to tomcat * default max queue size: Integer.MAX_VALUE, same to tomcat or default integrate only one ThreadPoolExecutor? because most customers TPS is not so high, no need to do this optimize -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-683) change all demo/integration test/sample, remove Log4jUtils.init, default to use logback
[ https://issues.apache.org/jira/browse/SCB-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-683: Description: and set default log level to info. not default to logback, change to log4j2 was:and set default log level to info. > change all demo/integration test/sample, remove Log4jUtils.init, default to > use logback > --- > > Key: SCB-683 > URL: https://issues.apache.org/jira/browse/SCB-683 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: wujimin >Assignee: 何一乐 >Priority: Major > Labels: newbie > > and set default log level to info. > > not default to logback, change to log4j2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (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
]
wujimin closed SCB-425.
---
Resolution: Duplicate
duplicate to https://issues.apache.org/jira/browse/SCB-638
> Add an easier way to read configurations
>
>
> Key: SCB-425
> URL: https://issues.apache.org/jira/browse/SCB-425
> Project: Apache ServiceComb
> Issue Type: New Feature
> Components: Java-Chassis
>Reporter: liubao
>Priority: Major
>
> Background:
> Read configurations for microservice or operation is quite common in code,
> e.g.
> {code:java}
> config = CONSUMER_FAULTINJECTION + serviceName + ".schemas." + schema + "."
> + CONSUMER_FAULTINJECTION_POLICY_PROTOCOLS +
> invocation.getTransport().getName() + "." + key;
> value = getConfigValue(config);
> if ((value != FAULT_INJECTION_DEFAULT_VALUE)) {
> return value;
> }
> config = CONSUMER_FAULTINJECTION + serviceName + "." +
> CONSUMER_FAULTINJECTION_POLICY_PROTOCOLS
> + invocation.getTransport().getName() + "." + key;
> value = getConfigValue(config);
> if ((value != FAULT_INJECTION_DEFAULT_VALUE)) {
> return value;
> }
> config = CONSUMER_FAULTINJECTION_GLOBAL +
> CONSUMER_FAULTINJECTION_POLICY_PROTOCOLS
> + invocation.getTransport().getName() + "." + key;
> {code}
> This code is very long and add callbacks if hard for user code.
>
> Suggestions:
> We need a easier way to read configurations, code snippets:
> {code:java}
> @Configuration(name="cse.myconfiguration")
> class MyConfiguration
> {
>@Configuration(name="prop1")
>String prop1;
>@Configuration(name="prop2")
>String prop2;
> }
> MyConfiguration configuration =
> ConfigurationFactory.getReference(invocation.getQualifiedMicroserviceName()){code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SCB-1137) optimize http2 performance
[ https://issues.apache.org/jira/browse/SCB-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1137: - Description: http2 is slower than http1.1 1."get connection" is slower than http1.1,very slow 2.request queued in producer thread pool, maybe there is condition race problem. was: http2 is slower than http1.1 "get connection" is slower than http1.1, it's so strange > optimize http2 performance > -- > > Key: SCB-1137 > URL: https://issues.apache.org/jira/browse/SCB-1137 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > > http2 is slower than http1.1 > 1."get connection" is slower than http1.1,very slow > 2.request queued in producer thread pool, maybe there is condition race > problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1134) change default verticle instance count
[ https://issues.apache.org/jira/browse/SCB-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1134. -- Resolution: Done Fix Version/s: java-chassis-1.2.0 > change default verticle instance count > -- > > Key: SCB-1134 > URL: https://issues.apache.org/jira/browse/SCB-1134 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > include: > * servicecomb.rest.server.thread-count > * servicecomb.rest.client.thread-count > * servicecomb.highway.server.thread-count > * servicecomb. highway.client.thread-count > change to: > * if cpu count less than 8, then thread-count set to cpu count > * if cpu count equals or big than 8, then thread-count set to 8 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-837) add http2 special configuration
[ https://issues.apache.org/jira/browse/SCB-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-837: Summary: add http2 special configuration (was: make http2 production ready) > add http2 special configuration > --- > > Key: SCB-837 > URL: https://issues.apache.org/jira/browse/SCB-837 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: wujimin >Assignee: 何一乐 >Priority: Major > > currenty, http2 client use all http1.1 settings, that cause http2 client > performance is so bad. > > we need to conside http2 client settings at least: > 1.concurrent stream in one connection, default value is 3, we must make it > bigger > 2.maxPoolSize, http1.1 need a big pool, but http2 need a big concurrent > stream count > > we must perform a performance test, that make sure got a good result, and > then set the setting to be our default setting. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-837) add http2 special configuration
[ https://issues.apache.org/jira/browse/SCB-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-837: Fix Version/s: java-chassis-1.2.0 > add http2 special configuration > --- > > Key: SCB-837 > URL: https://issues.apache.org/jira/browse/SCB-837 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: wujimin >Assignee: 何一乐 >Priority: Major > Fix For: java-chassis-1.2.0 > > > currenty, http2 client use all http1.1 settings, that cause http2 client > performance is so bad. > > we need to conside http2 client settings at least: > 1.concurrent stream in one connection, default value is 3, we must make it > bigger > 2.maxPoolSize, http1.1 need a big pool, but http2 need a big concurrent > stream count > > we must perform a performance test, that make sure got a good result, and > then set the setting to be our default setting. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1138) make http2 production ready
wujimin created SCB-1138: Summary: make http2 production ready Key: SCB-1138 URL: https://issues.apache.org/jira/browse/SCB-1138 Project: Apache ServiceComb Issue Type: Task Components: Java-Chassis Reporter: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1137) optimize http2 performance
wujimin created SCB-1137: Summary: optimize http2 performance Key: SCB-1137 URL: https://issues.apache.org/jira/browse/SCB-1137 Project: Apache ServiceComb Issue Type: Task Components: Java-Chassis Reporter: wujimin Assignee: wujimin http2 is slower than http1.1 "get connection" is slower than http1.1, it's so strange -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-837) add http2 special configuration
[ https://issues.apache.org/jira/browse/SCB-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-837. - Resolution: Done > add http2 special configuration > --- > > Key: SCB-837 > URL: https://issues.apache.org/jira/browse/SCB-837 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: 何一乐 >Priority: Major > Fix For: java-chassis-1.2.0 > > > currenty, http2 client use all http1.1 settings, that cause http2 client > performance is so bad. > > we need to conside http2 client settings at least: > 1.concurrent stream in one connection, default value is 3, we must make it > bigger > 2.maxPoolSize, http1.1 need a big pool, but http2 need a big concurrent > stream count > > we must perform a performance test, that make sure got a good result, and > then set the setting to be our default setting. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1137) optimize http2 performance
[ https://issues.apache.org/jira/browse/SCB-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1137: - Issue Type: Sub-task (was: Task) Parent: SCB-1138 > optimize http2 performance > -- > > Key: SCB-1137 > URL: https://issues.apache.org/jira/browse/SCB-1137 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > > http2 is slower than http1.1 > "get connection" is slower than http1.1, it's so strange -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-837) add http2 special configuration
[ https://issues.apache.org/jira/browse/SCB-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-837: Issue Type: Sub-task (was: Improvement) Parent: SCB-1138 > add http2 special configuration > --- > > Key: SCB-837 > URL: https://issues.apache.org/jira/browse/SCB-837 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: 何一乐 >Priority: Major > Fix For: java-chassis-1.2.0 > > > currenty, http2 client use all http1.1 settings, that cause http2 client > performance is so bad. > > we need to conside http2 client settings at least: > 1.concurrent stream in one connection, default value is 3, we must make it > bigger > 2.maxPoolSize, http1.1 need a big pool, but http2 need a big concurrent > stream count > > we must perform a performance test, that make sure got a good result, and > then set the setting to be our default setting. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1225) swagger generator core not depend on create dynamic class
[ https://issues.apache.org/jira/browse/SCB-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1225. -- Resolution: Done > swagger generator core not depend on create dynamic class > - > > Key: SCB-1225 > URL: https://issues.apache.org/jira/browse/SCB-1225 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1246) EventBus subscriber support order
wujimin created SCB-1246: Summary: EventBus subscriber support order Key: SCB-1246 URL: https://issues.apache.org/jira/browse/SCB-1246 Project: Apache ServiceComb Issue Type: Task Components: Java-Chassis Reporter: wujimin Assignee: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1246) EventBus subscriber support order
[ https://issues.apache.org/jira/browse/SCB-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1246: - Fix Version/s: java-chassis-1.3.0 > EventBus subscriber support order > - > > Key: SCB-1246 > URL: https://issues.apache.org/jira/browse/SCB-1246 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.3.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1246) EventBus subscriber support order
[ https://issues.apache.org/jira/browse/SCB-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1246. -- Resolution: Done > EventBus subscriber support order > - > > Key: SCB-1246 > URL: https://issues.apache.org/jira/browse/SCB-1246 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.3.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1242) provide spring data plugin to generate swagger and deserialize
[ https://issues.apache.org/jira/browse/SCB-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1242. -- Resolution: Done > provide spring data plugin to generate swagger and deserialize > -- > > Key: SCB-1242 > URL: https://issues.apache.org/jira/browse/SCB-1242 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1250) make ArchaiusUtils simpler
[ https://issues.apache.org/jira/browse/SCB-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1250. -- Resolution: Done > make ArchaiusUtils simpler > -- > > Key: SCB-1250 > URL: https://issues.apache.org/jira/browse/SCB-1250 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.3.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1255) swagger/jaxrs/springmvc annotations set in super class or interface
[ https://issues.apache.org/jira/browse/SCB-1255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1255: - Description: 1.multiple level super classes? 2.multiple interfaces? what's the priority of them? define annotation model, merge all anntations to model, and generate from model? if doing this, must copy hundreds line code from swagger.. was: 1.multiple level super classes? 2.multiple interfaces? what's the priority of them? define annotation model, merge all anntations to model, and generate from model? > swagger/jaxrs/springmvc annotations set in super class or interface > --- > > Key: SCB-1255 > URL: https://issues.apache.org/jira/browse/SCB-1255 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-2.0.0 > > > 1.multiple level super classes? > 2.multiple interfaces? > > what's the priority of them? > define annotation model, merge all anntations to model, and generate from > model? > if doing this, must copy hundreds line code from swagger.. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1227) swagger generator jaxrs not depend on create dynamic class
[ https://issues.apache.org/jira/browse/SCB-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1227. -- Resolution: Done > swagger generator jaxrs not depend on create dynamic class > -- > > Key: SCB-1227 > URL: https://issues.apache.org/jira/browse/SCB-1227 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1228) swagger generator springmvc not depend on create dynamic class
[ https://issues.apache.org/jira/browse/SCB-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1228. -- Resolution: Done > swagger generator springmvc not depend on create dynamic class > -- > > Key: SCB-1228 > URL: https://issues.apache.org/jira/browse/SCB-1228 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1256) rename ConcreteInterfaceRegister to ConcreteTypeRegister
wujimin created SCB-1256: Summary: rename ConcreteInterfaceRegister to ConcreteTypeRegister Key: SCB-1256 URL: https://issues.apache.org/jira/browse/SCB-1256 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: wujimin Assignee: wujimin Fix For: java-chassis-2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1255) swagger/jaxrs/springmvc annotations set in super class or interface
wujimin created SCB-1255: Summary: swagger/jaxrs/springmvc annotations set in super class or interface Key: SCB-1255 URL: https://issues.apache.org/jira/browse/SCB-1255 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: wujimin Assignee: wujimin Fix For: java-chassis-2.0.0 1.multiple level super classes? 2.multiple interfaces? what's the priority of them? define annotation model, merge all anntations to model, and generate from model? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1254) when integration with spring boot embeded sevlet container, support configure to extend from spring servlet
wujimin created SCB-1254: Summary: when integration with spring boot embeded sevlet container, support configure to extend from spring servlet Key: SCB-1254 URL: https://issues.apache.org/jira/browse/SCB-1254 Project: Apache ServiceComb Issue Type: Improvement Components: Java-Chassis Reporter: wujimin so that developers can use most existing mechanism of spring boot. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1257) clear MicroserviceVersion resources after related instance long time not up.
wujimin created SCB-1257: Summary: clear MicroserviceVersion resources after related instance long time not up. Key: SCB-1257 URL: https://issues.apache.org/jira/browse/SCB-1257 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: wujimin Assignee: wujimin Fix For: java-chassis-2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1251) reduce configuration inject callback
[ https://issues.apache.org/jira/browse/SCB-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1251. -- Resolution: Fixed > reduce configuration inject callback > > > Key: SCB-1251 > URL: https://issues.apache.org/jira/browse/SCB-1251 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.3.0 > > Attachments: image-2019-04-14-03-04-06-932.png, > image-2019-04-14-03-05-05-648.png > > Time Spent: 20m > Remaining Estimate: 0h > > currently, > if create MicroserviceVersion in AppManager failed, and try again and again > will create more and more callback, that cause memory leak > > add a inspectator module to view internal status of configuration mechanism > !image-2019-04-14-03-04-06-932.png! > !image-2019-04-14-03-05-05-648.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1252) change element of HttpParameterType to uppercase
wujimin created SCB-1252: Summary: change element of HttpParameterType to uppercase Key: SCB-1252 URL: https://issues.apache.org/jira/browse/SCB-1252 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: wujimin Assignee: wujimin Fix For: java-chassis-2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1252) change element of HttpParameterType to uppercase
[ https://issues.apache.org/jira/browse/SCB-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1252. -- Resolution: Done > change element of HttpParameterType to uppercase > > > Key: SCB-1252 > URL: https://issues.apache.org/jira/browse/SCB-1252 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1248) ServiceRegistry manage MicroserviceMeta
[ https://issues.apache.org/jira/browse/SCB-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1248. -- Resolution: Done > ServiceRegistry manage MicroserviceMeta > --- > > Key: SCB-1248 > URL: https://issues.apache.org/jira/browse/SCB-1248 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1260) inspector online test with servlet.urlPattern cause 404
wujimin created SCB-1260: Summary: inspector online test with servlet.urlPattern cause 404 Key: SCB-1260 URL: https://issues.apache.org/jira/browse/SCB-1260 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Affects Versions: java-chassis-1.2.0 Reporter: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1259) response type support Optional
wujimin created SCB-1259: Summary: response type support Optional Key: SCB-1259 URL: https://issues.apache.org/jira/browse/SCB-1259 Project: Apache ServiceComb Issue Type: Improvement Components: Java-Chassis Reporter: wujimin both consumer and producer support: # Optional getUser() # CompletableFuture> getUser() # CompletableFuture>> getUser() although Optional is no meaning to the producer, but sometimes, consumer and producer share the same interface in shared jar -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1261) change status code of timeout from 490 to standard 408
wujimin created SCB-1261: Summary: change status code of timeout from 490 to standard 408 Key: SCB-1261 URL: https://issues.apache.org/jira/browse/SCB-1261 Project: Apache ServiceComb Issue Type: Improvement Components: Java-Chassis Reporter: wujimin -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1256) rename ConcreteInterfaceRegister to ConcreteTypeRegister
[ https://issues.apache.org/jira/browse/SCB-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1256. -- Resolution: Done > rename ConcreteInterfaceRegister to ConcreteTypeRegister > > > Key: SCB-1256 > URL: https://issues.apache.org/jira/browse/SCB-1256 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1250) make ArchaiusUtils simpler
wujimin created SCB-1250: Summary: make ArchaiusUtils simpler Key: SCB-1250 URL: https://issues.apache.org/jira/browse/SCB-1250 Project: Apache ServiceComb Issue Type: Improvement Components: Java-Chassis Reporter: wujimin Assignee: wujimin Fix For: java-chassis-1.3.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1251) reduce configuration inject callback
[ https://issues.apache.org/jira/browse/SCB-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1251: - Attachment: image-2019-04-14-03-05-05-648.png > reduce configuration inject callback > > > Key: SCB-1251 > URL: https://issues.apache.org/jira/browse/SCB-1251 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.3.0 > > Attachments: image-2019-04-14-03-04-06-932.png, > image-2019-04-14-03-05-05-648.png > > > currently, > if create MicroserviceVersion in AppManager failed, and try again and again > will create more and more callback, that cause memory leak -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1251) reduce configuration inject callback
[ https://issues.apache.org/jira/browse/SCB-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1251: - Description: currently, if create MicroserviceVersion in AppManager failed, and try again and again will create more and more callback, that cause memory leak add a inspectator module to view internal status of configuration mechanism !image-2019-04-14-03-04-06-932.png! !image-2019-04-14-03-05-05-648.png! was: currently, if create MicroserviceVersion in AppManager failed, and try again and again will create more and more callback, that cause memory leak > reduce configuration inject callback > > > Key: SCB-1251 > URL: https://issues.apache.org/jira/browse/SCB-1251 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.3.0 > > Attachments: image-2019-04-14-03-04-06-932.png, > image-2019-04-14-03-05-05-648.png > > > currently, > if create MicroserviceVersion in AppManager failed, and try again and again > will create more and more callback, that cause memory leak > > add a inspectator module to view internal status of configuration mechanism > !image-2019-04-14-03-04-06-932.png! > !image-2019-04-14-03-05-05-648.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1251) reduce configuration inject callback
[ https://issues.apache.org/jira/browse/SCB-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1251: - Attachment: image-2019-04-14-03-04-06-932.png > reduce configuration inject callback > > > Key: SCB-1251 > URL: https://issues.apache.org/jira/browse/SCB-1251 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-1.3.0 > > Attachments: image-2019-04-14-03-04-06-932.png > > > currently, > if create MicroserviceVersion in AppManager failed, and try again and again > will create more and more callback, that cause memory leak -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1193) upgread spring boot versions and add easy to use dependency management
[ https://issues.apache.org/jira/browse/SCB-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1193. -- Resolution: Done Fix Version/s: java-chassis-1.2.0 > upgread spring boot versions and add easy to use dependency management > -- > > Key: SCB-1193 > URL: https://issues.apache.org/jira/browse/SCB-1193 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: liubao >Assignee: liubao >Priority: Major > Fix For: java-chassis-1.2.0 > > Time Spent: 20m > Remaining Estimate: 0h > > # upgrade spring boot to 2.1.2.RELEASE, because current version is a bit old > and will in mentainence in future > # add dependency management pom for spring 4, spring 5, spring boot 1 & > spring boot 2, to easy developers use > # add parent for spring 4, spring 5, spring boot1, spring boot 2 for > internal use. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1290) add swagger generator unit test case for List>
[ https://issues.apache.org/jira/browse/SCB-1290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1290. -- Resolution: Done > add swagger generator unit test case for List> > --- > > Key: SCB-1290 > URL: https://issues.apache.org/jira/browse/SCB-1290 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-316) As a SDK user, I want to look the details view of a microservice's latency so that metrics must collect the recently data
[ https://issues.apache.org/jira/browse/SCB-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16860710#comment-16860710 ] wujimin commented on SCB-316: - [https://zhuanlan.zhihu.com/p/26763580] > As a SDK user, I want to look the details view of a microservice's latency so > that metrics must collect the recently data > - > > Key: SCB-316 > URL: https://issues.apache.org/jira/browse/SCB-316 > Project: Apache ServiceComb > Issue Type: New Feature > Components: Java-Chassis >Reporter: jeho0815 >Priority: Major > > in microservice, we need look out the 99.9% 99.5% 99% 95% 90% 75% 50% 25% > 5%... latency, i think ServiceComb metrics has to support this. > [~zhengyangyong] > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1323) should ignore parameter of HttpServletRequest when generate swagger
wujimin created SCB-1323: Summary: should ignore parameter of HttpServletRequest when generate swagger Key: SCB-1323 URL: https://issues.apache.org/jira/browse/SCB-1323 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Affects Versions: java-chassis-2.0.0 Reporter: wujimin Assignee: wujimin Fix For: java-chassis-2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-1324) basePath should be a single slash when basePath not specialed annotation by RestController
wujimin created SCB-1324: Summary: basePath should be a single slash when basePath not specialed annotation by RestController Key: SCB-1324 URL: https://issues.apache.org/jira/browse/SCB-1324 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Reporter: wujimin Assignee: wujimin Fix For: java-chassis-2.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1323) should ignore parameter of HttpServletRequest when generate swagger
[ https://issues.apache.org/jira/browse/SCB-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1323: - Affects Version/s: (was: java-chassis-2.0.0) > should ignore parameter of HttpServletRequest when generate swagger > --- > > Key: SCB-1323 > URL: https://issues.apache.org/jira/browse/SCB-1323 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-1324) basePath should be a single slash when basePath not specified and annotation by RestController
[ https://issues.apache.org/jira/browse/SCB-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin updated SCB-1324: - Summary: basePath should be a single slash when basePath not specified and annotation by RestController (was: basePath should be a single slash when basePath not specialed annotation by RestController) > basePath should be a single slash when basePath not specified and annotation > by RestController > -- > > Key: SCB-1324 > URL: https://issues.apache.org/jira/browse/SCB-1324 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-2.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-1284) operationId should not be empty
[ https://issues.apache.org/jira/browse/SCB-1284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wujimin resolved SCB-1284. -- Resolution: Done > operationId should not be empty > --- > > Key: SCB-1284 > URL: https://issues.apache.org/jira/browse/SCB-1284 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: wujimin >Priority: Major > Fix For: java-chassis-2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
