[jira] [Resolved] (SCB-910) Java Chassis support spring boot 2.0
[ https://issues.apache.org/jira/browse/SCB-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng resolved SCB-910. --- Resolution: Fixed > Java Chassis support spring boot 2.0 > > > Key: SCB-910 > URL: https://issues.apache.org/jira/browse/SCB-910 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.1.0 > > > Java Chassis support both spring boot 1.5.x and spring boot 2.0.x -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (SCB-690) when producer invocation prepare to run in executor, make sure not disconnect/ not time out
[ https://issues.apache.org/jira/browse/SCB-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reopened SCB-690: --- Assignee: (was: yangyongzheng) > when producer invocation prepare to run in executor, make sure not > disconnect/ not time out > --- > > Key: SCB-690 > URL: https://issues.apache.org/jira/browse/SCB-690 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Priority: Major > > vertx rest and highway not control producer timeout > > note: if already running, then could do nothing, just let it go till finished. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (SCB-765) add connection count meter to metrics
[ https://issues.apache.org/jira/browse/SCB-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reopened SCB-765: --- Assignee: (was: yangyongzheng) > add connection count meter to metrics > - > > Key: SCB-765 > URL: https://issues.apache.org/jira/browse/SCB-765 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Priority: Major > > include consumer and producer, highway and rest > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-849) refactor producer connection limit using vertx metrics spi mechanism
[ https://issues.apache.org/jira/browse/SCB-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng closed SCB-849. - Resolution: Won't Fix https://issues.apache.org/jira/browse/SCB-894 > refactor producer connection limit using vertx metrics spi mechanism > > > Key: SCB-849 > URL: https://issues.apache.org/jira/browse/SCB-849 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.1.0 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.1.0 > > > we can use vertx metrics spi mechanism to simplify connection limit feature -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-765) add connection count meter to metrics
[ https://issues.apache.org/jira/browse/SCB-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng closed SCB-765. - Resolution: Won't Fix https://issues.apache.org/jira/browse/SCB-894 > add connection count meter to metrics > - > > Key: SCB-765 > URL: https://issues.apache.org/jira/browse/SCB-765 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: yangyongzheng >Priority: Major > > include consumer and producer, highway and rest > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-690) when producer invocation prepare to run in executor, make sure not disconnect/ not time out
[ https://issues.apache.org/jira/browse/SCB-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng closed SCB-690. - Resolution: Won't Fix https://issues.apache.org/jira/browse/SCB-894 > when producer invocation prepare to run in executor, make sure not > disconnect/ not time out > --- > > Key: SCB-690 > URL: https://issues.apache.org/jira/browse/SCB-690 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: yangyongzheng >Priority: Major > > vertx rest and highway not control producer timeout > > note: if already running, then could do nothing, just let it go till finished. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-910) Java Chassis support spring boot 2.0
yangyongzheng created SCB-910: - Summary: Java Chassis support spring boot 2.0 Key: SCB-910 URL: https://issues.apache.org/jira/browse/SCB-910 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Affects Versions: java-chassis-1.0.0 Reporter: yangyongzheng Assignee: yangyongzheng Fix For: java-chassis-1.1.0 Java Chassis support both spring boot 1.5.x and spring boot 2.0.x -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-849) refactor producer connection limit using vertx metrics spi mechanism
yangyongzheng created SCB-849: - Summary: refactor producer connection limit using vertx metrics spi mechanism Key: SCB-849 URL: https://issues.apache.org/jira/browse/SCB-849 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Affects Versions: java-chassis-1.1.0 Reporter: yangyongzheng Assignee: yangyongzheng Fix For: java-chassis-1.1.0 we can use vertx metrics spi mechanism to simplify connection limit feature -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-556) Update the english version of FAQ
[ https://issues.apache.org/jira/browse/SCB-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-556: - Assignee: lidian (was: yangyongzheng) > Update the english version of FAQ > --- > > Key: SCB-556 > URL: https://issues.apache.org/jira/browse/SCB-556 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: website >Reporter: Willem Jiang >Assignee: lidian >Priority: Major > > Current we add some new entries on the Chinese version of FAQ, the English > version of FAQ need to be updated. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-831) Saga UT failed at LoadBalancedClusterMessageSenderTest on Windows environment
[
https://issues.apache.org/jira/browse/SCB-831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yangyongzheng updated SCB-831:
--
Summary: Saga UT failed at LoadBalancedClusterMessageSenderTest on Windows
environment (was: Saga UT failed at LoadBalancedClusterMessageSenderTest on
WIndows environment)
> Saga UT failed at LoadBalancedClusterMessageSenderTest on Windows environment
> -
>
> Key: SCB-831
> URL: https://issues.apache.org/jira/browse/SCB-831
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Saga
>Affects Versions: saga-0.2.0
> Environment: Windows 7 or Windows Server 2008 R2
>Reporter: yangyongzheng
>Priority: Major
>
> UT will failed at :
> LoadBalancedClusterMessageSenderTest.stopSendingWhenClusterIsDown
> It seems this assert
> await().atMost(2, SECONDS).until(new Callable() {
> @Override
> public Boolean call() throws Exception {
> return connected.get(8080).size() == 2 || connected.get(8090).size()
> == 2;
> }
> });
> The connected size will only be 1 not 2
> I had found out that GrpcCompensateStreamObserver don't trigger onError when
> simulate connection closed in this case so LoadBalancedClusterMessageSender
> can't take PushBackReconnectRunnable from pendingTasks in order to reconnect
> server, then the connected count will be only 1, then test case failed
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SCB-831) Saga UT failed at LoadBalancedClusterMessageSenderTest on WIndows environment
yangyongzheng created SCB-831:
-
Summary: Saga UT failed at LoadBalancedClusterMessageSenderTest on
WIndows environment
Key: SCB-831
URL: https://issues.apache.org/jira/browse/SCB-831
Project: Apache ServiceComb
Issue Type: Bug
Components: Saga
Affects Versions: saga-0.2.0
Environment: Windows 7 or Windows Server 2008 R2
Reporter: yangyongzheng
UT will failed at :
LoadBalancedClusterMessageSenderTest.stopSendingWhenClusterIsDown
It seems this assert
await().atMost(2, SECONDS).until(new Callable() {
@Override
public Boolean call() throws Exception {
return connected.get(8080).size() == 2 || connected.get(8090).size() ==
2;
}
});
The connected size will only be 1 not 2
I had found out that GrpcCompensateStreamObserver don't trigger onError when
simulate connection closed in this case so LoadBalancedClusterMessageSender
can't take PushBackReconnectRunnable from pendingTasks in order to reconnect
server, then the connected count will be only 1, then test case failed
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SCB-830) Update Chassis from 1.0.0-m2 to 1.0.0 in Saga
[ https://issues.apache.org/jira/browse/SCB-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng updated SCB-830: -- Summary: Update Chassis from 1.0.0-m2 to 1.0.0 in Saga (was: Update Chassis from 1.0.0-m2 to 1.0.0 in Sga) > Update Chassis from 1.0.0-m2 to 1.0.0 in Saga > - > > Key: SCB-830 > URL: https://issues.apache.org/jira/browse/SCB-830 > Project: Apache ServiceComb > Issue Type: Bug > Components: Saga >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: saga-0.3.0 > > > Update Chassis from 1.0.0-m2 to 1.0.0 in Sga -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-830) Update Chassis from 1.0.0-m2 to 1.0.0 in Saga
[ https://issues.apache.org/jira/browse/SCB-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng updated SCB-830: -- Description: Update Chassis from 1.0.0-m2 to 1.0.0 in Saga (was: Update Chassis from 1.0.0-m2 to 1.0.0 in Sga) > Update Chassis from 1.0.0-m2 to 1.0.0 in Saga > - > > Key: SCB-830 > URL: https://issues.apache.org/jira/browse/SCB-830 > Project: Apache ServiceComb > Issue Type: Bug > Components: Saga >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: saga-0.3.0 > > > Update Chassis from 1.0.0-m2 to 1.0.0 in Saga -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-830) Update Chassis from 1.0.0-m2 to 1.0.0 in Sga
yangyongzheng created SCB-830: - Summary: Update Chassis from 1.0.0-m2 to 1.0.0 in Sga Key: SCB-830 URL: https://issues.apache.org/jira/browse/SCB-830 Project: Apache ServiceComb Issue Type: Bug Components: Saga Reporter: yangyongzheng Assignee: yangyongzheng Fix For: saga-0.3.0 Update Chassis from 1.0.0-m2 to 1.0.0 in Sga -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-765) add connection count meter to metrics
[ https://issues.apache.org/jira/browse/SCB-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-765: - Assignee: yangyongzheng > add connection count meter to metrics > - > > Key: SCB-765 > URL: https://issues.apache.org/jira/browse/SCB-765 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: yangyongzheng >Priority: Major > > include consumer and producer, highway and rest > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-781) 关于apollo配置中心不支持@ConfigurationProperties
[ https://issues.apache.org/jira/browse/SCB-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-781: - Assignee: Sean Li > 关于apollo配置中心不支持@ConfigurationProperties > --- > > Key: SCB-781 > URL: https://issues.apache.org/jira/browse/SCB-781 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 > Environment: windows7 >Reporter: by.lv >Assignee: Sean Li >Priority: Major > Fix For: java-chassis-1.1.0 > > > 集成了apollo配置中心后,启动发现无法识别sb 的@ConfigurationProperties 导致一些插件初始化报错. > 我把mybatis的配置放到apollo里面了.但是启动的时候,sb加载mybatis的配置读取到为空.但是我直接放到项目的配置文件里面就可以. > !https://user-images.githubusercontent.com/6836934/43314696-47fc8904-91c6-11e8-83aa-37747df75ea5.png! > !https://user-images.githubusercontent.com/6836934/43314708-50581f64-91c6-11e8-8e1d-f504aec344eb.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-688) vertx rest server not accept too many connection
[ https://issues.apache.org/jira/browse/SCB-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng resolved SCB-688. --- Resolution: Fixed > vertx rest server not accept too many connection > > > Key: SCB-688 > URL: https://issues.apache.org/jira/browse/SCB-688 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: yangyongzheng >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-690) when producer invocation prepare to run in executor, make sure not disconnect/ not time out
[ https://issues.apache.org/jira/browse/SCB-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-690: - Assignee: yangyongzheng > when producer invocation prepare to run in executor, make sure not > disconnect/ not time out > --- > > Key: SCB-690 > URL: https://issues.apache.org/jira/browse/SCB-690 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: yangyongzheng >Priority: Major > > vertx rest and highway not control producer timeout > > note: if already running, then could do nothing, just let it go till finished. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-689) servlet rest server not accept too many connection
[ https://issues.apache.org/jira/browse/SCB-689?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569633#comment-16569633 ] yangyongzheng commented on SCB-689: --- I think web container(server) such as Tomcat had connection limit setting, may not necessary implement this feature ？ > servlet rest server not accept too many connection > -- > > Key: SCB-689 > URL: https://issues.apache.org/jira/browse/SCB-689 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Priority: Major > > maybe just need to write document explain how to use -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-687) highway server not accept too many connection
[ https://issues.apache.org/jira/browse/SCB-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng resolved SCB-687. --- Resolution: Fixed > highway server not accept too many connection > - > > Key: SCB-687 > URL: https://issues.apache.org/jira/browse/SCB-687 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-244) [pack] add demo to use pack with java chassis
[ https://issues.apache.org/jira/browse/SCB-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng closed SCB-244. - Resolution: Fixed > [pack] add demo to use pack with java chassis > - > > Key: SCB-244 > URL: https://issues.apache.org/jira/browse/SCB-244 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Saga >Affects Versions: saga-0.2.0 >Reporter: Eric Lee >Assignee: yangyongzheng >Priority: Minor > Fix For: saga-0.3.0 > > > as a dev, I want to know how I can use pack with Java Chassis. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-688) vertx rest server not accept too many connection
[ https://issues.apache.org/jira/browse/SCB-688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-688: - Assignee: yangyongzheng > vertx rest server not accept too many connection > > > Key: SCB-688 > URL: https://issues.apache.org/jira/browse/SCB-688 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: yangyongzheng >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-687) highway server not accept too many connection
[ https://issues.apache.org/jira/browse/SCB-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng updated SCB-687: -- Fix Version/s: java-chassis-1.1.0 > highway server not accept too many connection > - > > Key: SCB-687 > URL: https://issues.apache.org/jira/browse/SCB-687 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-773) Java Chassis::Core test failed
[ https://issues.apache.org/jira/browse/SCB-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-773: - Assignee: yangyongzheng > Java Chassis::Core test failed > -- > > Key: SCB-773 > URL: https://issues.apache.org/jira/browse/SCB-773 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 > Environment: Java : > openjdk version "1.8.0_171" > OpenJDK Runtime Environment (build 1.8.0_171-b10) > OpenJDK 64-Bit Server VM (build 25.171-b10, mixed mode) > OS: > CentOS Linux release 7.5.1804 (Core) >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0 > > > 2018-07-24 17:23:24,957 [main ] INFO LocalServiceRegistryClientImpl - create > empty local registry. > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.516 sec - > in org.apache.servicecomb.core.TestSCBEngine > Running org.apache.servicecomb.core.TestExecutors > 2018-07-24 17:23:25,091 [main ] INFO FixedThreadExecutor - executor group 2, > thread per group 2. > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in > org.apache.servicecomb.core.TestExecutors > Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.302 sec - > in org.apache.servicecomb.core.TestInvocationFactory > Results : > Tests in error: > TestConsumerSchemaFactory.createConsumerSchema:45 NullPointer > Tests run: 119, Failures: 0, Errors: 1, Skipped: 0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-773) Java Chassis::Core test failed
[ https://issues.apache.org/jira/browse/SCB-773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555213#comment-16555213 ] yangyongzheng commented on SCB-773: --- solved in https://issues.apache.org/jira/browse/SCB-772 > Java Chassis::Core test failed > -- > > Key: SCB-773 > URL: https://issues.apache.org/jira/browse/SCB-773 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 > Environment: Java : > openjdk version "1.8.0_171" > OpenJDK Runtime Environment (build 1.8.0_171-b10) > OpenJDK 64-Bit Server VM (build 25.171-b10, mixed mode) > OS: > CentOS Linux release 7.5.1804 (Core) >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0 > > > 2018-07-24 17:23:24,957 [main ] INFO LocalServiceRegistryClientImpl - create > empty local registry. > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.516 sec - > in org.apache.servicecomb.core.TestSCBEngine > Running org.apache.servicecomb.core.TestExecutors > 2018-07-24 17:23:25,091 [main ] INFO FixedThreadExecutor - executor group 2, > thread per group 2. > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in > org.apache.servicecomb.core.TestExecutors > Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.302 sec - > in org.apache.servicecomb.core.TestInvocationFactory > Results : > Tests in error: > TestConsumerSchemaFactory.createConsumerSchema:45 NullPointer > Tests run: 119, Failures: 0, Errors: 1, Skipped: 0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-773) Java Chassis::Core test failed
[ https://issues.apache.org/jira/browse/SCB-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng resolved SCB-773. --- Resolution: Fixed > Java Chassis::Core test failed > -- > > Key: SCB-773 > URL: https://issues.apache.org/jira/browse/SCB-773 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 > Environment: Java : > openjdk version "1.8.0_171" > OpenJDK Runtime Environment (build 1.8.0_171-b10) > OpenJDK 64-Bit Server VM (build 25.171-b10, mixed mode) > OS: > CentOS Linux release 7.5.1804 (Core) >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0 > > > 2018-07-24 17:23:24,957 [main ] INFO LocalServiceRegistryClientImpl - create > empty local registry. > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.516 sec - > in org.apache.servicecomb.core.TestSCBEngine > Running org.apache.servicecomb.core.TestExecutors > 2018-07-24 17:23:25,091 [main ] INFO FixedThreadExecutor - executor group 2, > thread per group 2. > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in > org.apache.servicecomb.core.TestExecutors > Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.302 sec - > in org.apache.servicecomb.core.TestInvocationFactory > Results : > Tests in error: > TestConsumerSchemaFactory.createConsumerSchema:45 NullPointer > Tests run: 119, Failures: 0, Errors: 1, Skipped: 0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-772) Java Chassis::Handlers::Loadbalance test failed
[ https://issues.apache.org/jira/browse/SCB-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng resolved SCB-772. --- Resolution: Fixed > Java Chassis::Handlers::Loadbalance test failed > --- > > Key: SCB-772 > URL: https://issues.apache.org/jira/browse/SCB-772 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 > Environment: JDK : > java version "1.8.0_171" > Java(TM) SE Runtime Environment (build 1.8.0_171-b11) > Java HotSpot(TM) 64-Bit Server VM (build 25.171-b11, mixed mode) > OS : > Linux version 4.4.0-104-generic (buildd@lgw01-amd64-022) (gcc version 5.4.0 > 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) ) #127-Ubuntu SMP Mon Dec 11 > 12:16:42 UTC 2017 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Critical > Fix For: java-chassis-1.0.0 > > > Java Chassis::Handlers::Loadbalance test failed: > 2018-07-24 09:45:08,429 [main ] ERROR ExceptionUtils - > Exception: org.apache.servicecomb.core.exception.CseException; No available > address found. microserviceName=ms, version=null, discoveryGroupName=null > ServiceDefinitionException Code:servicecomb.lb.no.available.address, > Message:No available address found. microserviceName=ms, version=null, > discoveryGroupName=null > at > org.apache.servicecomb.core.exception.ExceptionUtils.createCseException(ExceptionUtils.java:57) > at > org.apache.servicecomb.core.exception.ExceptionUtils.lbAddressNotFound(ExceptionUtils.java:88) > at > org.apache.servicecomb.loadbalance.LoadbalanceHandler.send(LoadbalanceHandler.java:135) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at mockit.internal.util.MethodReflection.invoke(MethodReflection.java:120) > at mockit.internal.util.MethodReflection.invoke(MethodReflection.java:185) > at mockit.Deencapsulation.invoke(Deencapsulation.java:210) > at > org.apache.servicecomb.loadbalance.TestLoadbalanceHandler.send_noEndPoint(TestLoadbalanceHandler.java:195) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > mockit.integration.junit4.internal.JUnit4TestRunnerDecorator.executeTestMethod(JUnit4TestRunnerDecorator.java:162) > at > mockit.integration.junit4.internal.JUnit4TestRunnerDecorator.invokeExplosively(JUnit4TestRunnerDecorator.java:71) > at > mockit.integration.junit4.internal.MockFrameworkMethod.invokeExplosively(MockFrameworkMethod.java:37) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at > org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > at > org.apache.maven.surefire.booter.Forked
[jira] [Created] (SCB-773) Java Chassis::Core test failed
yangyongzheng created SCB-773: - Summary: Java Chassis::Core test failed Key: SCB-773 URL: https://issues.apache.org/jira/browse/SCB-773 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Affects Versions: java-chassis-1.0.0-m2 Environment: Java : openjdk version "1.8.0_171" OpenJDK Runtime Environment (build 1.8.0_171-b10) OpenJDK 64-Bit Server VM (build 25.171-b10, mixed mode) OS: CentOS Linux release 7.5.1804 (Core) Reporter: yangyongzheng Fix For: java-chassis-1.0.0 2018-07-24 17:23:24,957 [main ] INFO LocalServiceRegistryClientImpl - create empty local registry. Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.516 sec - in org.apache.servicecomb.core.TestSCBEngine Running org.apache.servicecomb.core.TestExecutors 2018-07-24 17:23:25,091 [main ] INFO FixedThreadExecutor - executor group 2, thread per group 2. Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in org.apache.servicecomb.core.TestExecutors Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.302 sec - in org.apache.servicecomb.core.TestInvocationFactory Results : Tests in error: TestConsumerSchemaFactory.createConsumerSchema:45 NullPointer Tests run: 119, Failures: 0, Errors: 1, Skipped: 0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-772) Java Chassis::Handlers::Loadbalance test failed
[ https://issues.apache.org/jira/browse/SCB-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-772: - Assignee: yangyongzheng (was: liubao) > Java Chassis::Handlers::Loadbalance test failed > --- > > Key: SCB-772 > URL: https://issues.apache.org/jira/browse/SCB-772 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 > Environment: JDK : > java version "1.8.0_171" > Java(TM) SE Runtime Environment (build 1.8.0_171-b11) > Java HotSpot(TM) 64-Bit Server VM (build 25.171-b11, mixed mode) > OS : > Linux version 4.4.0-104-generic (buildd@lgw01-amd64-022) (gcc version 5.4.0 > 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) ) #127-Ubuntu SMP Mon Dec 11 > 12:16:42 UTC 2017 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Critical > Fix For: java-chassis-1.0.0 > > > Java Chassis::Handlers::Loadbalance test failed: > 2018-07-24 09:45:08,429 [main ] ERROR ExceptionUtils - > Exception: org.apache.servicecomb.core.exception.CseException; No available > address found. microserviceName=ms, version=null, discoveryGroupName=null > ServiceDefinitionException Code:servicecomb.lb.no.available.address, > Message:No available address found. microserviceName=ms, version=null, > discoveryGroupName=null > at > org.apache.servicecomb.core.exception.ExceptionUtils.createCseException(ExceptionUtils.java:57) > at > org.apache.servicecomb.core.exception.ExceptionUtils.lbAddressNotFound(ExceptionUtils.java:88) > at > org.apache.servicecomb.loadbalance.LoadbalanceHandler.send(LoadbalanceHandler.java:135) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at mockit.internal.util.MethodReflection.invoke(MethodReflection.java:120) > at mockit.internal.util.MethodReflection.invoke(MethodReflection.java:185) > at mockit.Deencapsulation.invoke(Deencapsulation.java:210) > at > org.apache.servicecomb.loadbalance.TestLoadbalanceHandler.send_noEndPoint(TestLoadbalanceHandler.java:195) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > mockit.integration.junit4.internal.JUnit4TestRunnerDecorator.executeTestMethod(JUnit4TestRunnerDecorator.java:162) > at > mockit.integration.junit4.internal.JUnit4TestRunnerDecorator.invokeExplosively(JUnit4TestRunnerDecorator.java:71) > at > mockit.integration.junit4.internal.MockFrameworkMethod.invokeExplosively(MockFrameworkMethod.java:37) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java) > at > org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at > org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239) > at org.junit.rules.RunRules.evaluate(RunRules.java:20) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at > org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) > at > org.apache.ma
[jira] [Resolved] (SCB-763) Simplify Dynamic Config (Apollo) Integration Test in Java Chassis
[ https://issues.apache.org/jira/browse/SCB-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng resolved SCB-763. --- Resolution: Fixed > Simplify Dynamic Config (Apollo) Integration Test in Java Chassis > - > > Key: SCB-763 > URL: https://issues.apache.org/jira/browse/SCB-763 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0 > > > Simplify Dynamic Config (Apollo) Integration Test in Java Chassis > Discussion Is here： > https://lists.apache.org/thread.html/d6adfe1c23a68b00271cac70840b8ed531939d565f80fa49171f68c1@%3Cdev.servicecomb.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-772) Java Chassis::Handlers::Loadbalance test failed
yangyongzheng created SCB-772: - Summary: Java Chassis::Handlers::Loadbalance test failed Key: SCB-772 URL: https://issues.apache.org/jira/browse/SCB-772 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Affects Versions: java-chassis-1.0.0-m2 Environment: JDK : java version "1.8.0_171" Java(TM) SE Runtime Environment (build 1.8.0_171-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.171-b11, mixed mode) OS : Linux version 4.4.0-104-generic (buildd@lgw01-amd64-022) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) ) #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 Reporter: yangyongzheng Fix For: java-chassis-1.0.0 Java Chassis::Handlers::Loadbalance test failed: 2018-07-24 09:45:08,429 [main ] ERROR ExceptionUtils - Exception: org.apache.servicecomb.core.exception.CseException; No available address found. microserviceName=ms, version=null, discoveryGroupName=null ServiceDefinitionException Code:servicecomb.lb.no.available.address, Message:No available address found. microserviceName=ms, version=null, discoveryGroupName=null at org.apache.servicecomb.core.exception.ExceptionUtils.createCseException(ExceptionUtils.java:57) at org.apache.servicecomb.core.exception.ExceptionUtils.lbAddressNotFound(ExceptionUtils.java:88) at org.apache.servicecomb.loadbalance.LoadbalanceHandler.send(LoadbalanceHandler.java:135) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at mockit.internal.util.MethodReflection.invoke(MethodReflection.java:120) at mockit.internal.util.MethodReflection.invoke(MethodReflection.java:185) at mockit.Deencapsulation.invoke(Deencapsulation.java:210) at org.apache.servicecomb.loadbalance.TestLoadbalanceHandler.send_noEndPoint(TestLoadbalanceHandler.java:195) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at mockit.integration.junit4.internal.JUnit4TestRunnerDecorator.executeTestMethod(JUnit4TestRunnerDecorator.java:162) at mockit.integration.junit4.internal.JUnit4TestRunnerDecorator.invokeExplosively(JUnit4TestRunnerDecorator.java:71) at mockit.integration.junit4.internal.MockFrameworkMethod.invokeExplosively(MockFrameworkMethod.java:37) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:239) at org.junit.rules.RunRules.evaluate(RunRules.java:20) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) at org.junit.runners.ParentRunner.run(ParentRunner.java:363) at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367) at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161) at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290) at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121) 2018-07-24 09:45:08,493 [main ] INFO DiscoveryTree - DiscoveryFilter org.apache.servicecomb.loadbalance.filter.ServerDiscoveryFilter, enabled true. 2018-07-24 09:45:08,542 [main ] INFO
[jira] [Created] (SCB-763) Simplify Dynamic Config (Apollo) Integration Test in Java Chassis
yangyongzheng created SCB-763: - Summary: Simplify Dynamic Config (Apollo) Integration Test in Java Chassis Key: SCB-763 URL: https://issues.apache.org/jira/browse/SCB-763 Project: Apache ServiceComb Issue Type: Improvement Components: Java-Chassis Affects Versions: java-chassis-1.0.0-m2 Reporter: yangyongzheng Assignee: yangyongzheng Fix For: java-chassis-1.0.0 Simplify Dynamic Config (Apollo) Integration Test in Java Chassis Discussion Is here： https://lists.apache.org/thread.html/d6adfe1c23a68b00271cac70840b8ed531939d565f80fa49171f68c1@%3Cdev.servicecomb.apache.org%3E -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-687) highway server not accept too many connection
[ https://issues.apache.org/jira/browse/SCB-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-687: - Assignee: yangyongzheng > highway server not accept too many connection > - > > Key: SCB-687 > URL: https://issues.apache.org/jira/browse/SCB-687 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Reporter: wujimin >Assignee: yangyongzheng >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-686) producer protected
[ https://issues.apache.org/jira/browse/SCB-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16547291#comment-16547291 ] yangyongzheng commented on SCB-686: --- https://github.com/eclipse/vert.x/issues/2542 > producer protected > -- > > Key: SCB-686 > URL: https://issues.apache.org/jira/browse/SCB-686 > Project: Apache ServiceComb > Issue Type: Task > Components: Java-Chassis >Reporter: wujimin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-664) demo for integration with zuul
[ https://issues.apache.org/jira/browse/SCB-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng closed SCB-664. - Resolution: Won't Fix > demo for integration with zuul > -- > > Key: SCB-664 > URL: https://issues.apache.org/jira/browse/SCB-664 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: miaoyanjie >Assignee: yangyongzheng >Priority: Major > > 需要一个集成java-chassis 和 zuul做网关的demo, 或者直接做成pom包。 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-664) demo for integration with zuul
[ https://issues.apache.org/jira/browse/SCB-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-664: - Assignee: yangyongzheng > demo for integration with zuul > -- > > Key: SCB-664 > URL: https://issues.apache.org/jira/browse/SCB-664 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: miaoyanjie >Assignee: yangyongzheng >Priority: Major > > 需要一个集成java-chassis 和 zuul做网关的demo, 或者直接做成pom包。 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-746) Update Chassis from m1 to m2 in start.servicecomb.io
[ https://issues.apache.org/jira/browse/SCB-746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545078#comment-16545078 ] yangyongzheng commented on SCB-746: --- OK, thanks~ > Update Chassis from m1 to m2 in start.servicecomb.io > > > Key: SCB-746 > URL: https://issues.apache.org/jira/browse/SCB-746 > Project: Apache ServiceComb > Issue Type: Wish > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0 > > > Update Chassis from m1 to m2 in start.servicecomb.io -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-746) Update Chassis from m1 to m2 in start.servicecomb.io
[ https://issues.apache.org/jira/browse/SCB-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng closed SCB-746. - Resolution: Fixed Done > Update Chassis from m1 to m2 in start.servicecomb.io > > > Key: SCB-746 > URL: https://issues.apache.org/jira/browse/SCB-746 > Project: Apache ServiceComb > Issue Type: Wish > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0 > > > Update Chassis from m1 to m2 in start.servicecomb.io -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-746) Update Chassis from m1 to m2 in start.servicecomb.io
[ https://issues.apache.org/jira/browse/SCB-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-746: - Assignee: yangyongzheng > Update Chassis from m1 to m2 in start.servicecomb.io > > > Key: SCB-746 > URL: https://issues.apache.org/jira/browse/SCB-746 > Project: Apache ServiceComb > Issue Type: Wish > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0 > > > Update Chassis from m1 to m2 in start.servicecomb.io -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-746) Update Chassis from m1 to m2 in start.servicecomb.io
yangyongzheng created SCB-746: - Summary: Update Chassis from m1 to m2 in start.servicecomb.io Key: SCB-746 URL: https://issues.apache.org/jira/browse/SCB-746 Project: Apache ServiceComb Issue Type: Wish Components: Java-Chassis Affects Versions: java-chassis-1.0.0-m2 Reporter: yangyongzheng Fix For: java-chassis-1.0.0 Update Chassis from m1 to m2 in start.servicecomb.io -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-592) Spring Zuul Tracing Integration Tests CI failed
[ https://issues.apache.org/jira/browse/SCB-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542750#comment-16542750 ] yangyongzheng commented on SCB-592: --- tested but can not reproduce > Spring Zuul Tracing Integration Tests CI failed > --- > > Key: SCB-592 > URL: https://issues.apache.org/jira/browse/SCB-592 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0 > > > Spring Zuul Tracing Integration Tests is easy failed by : > *Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on > project spring-zuul-tracing-tests Execution* > *Exception Error occurred in starting fork, check output in log* > > we need fix it -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 ] yangyongzheng closed SCB-592. - Resolution: Won't Fix > Spring Zuul Tracing Integration Tests CI failed > --- > > Key: SCB-592 > URL: https://issues.apache.org/jira/browse/SCB-592 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0 > > > Spring Zuul Tracing Integration Tests is easy failed by : > *Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on > project spring-zuul-tracing-tests Execution* > *Exception Error occurred in starting fork, check output in log* > > we need fix it -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-629) 通过Zuul网关传递String类型的json参数，不能被正确接收
[ https://issues.apache.org/jira/browse/SCB-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng closed SCB-629. - Resolution: Won't Fix > 通过Zuul网关传递String类型的json参数，不能被正确接收 > - > > Key: SCB-629 > URL: https://issues.apache.org/jira/browse/SCB-629 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m1 >Reporter: lixing >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0 > > > 使用net.sf.json.JSONObject 发送String类型的JSONobject参数，会出现jackson > jar包报出的转换错误的Excepiton，能不能支持String类型的json参数传递，在使用zuul作为网关的时候 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (SCB-629) 通过Zuul网关传递String类型的json参数，不能被正确接收
[ https://issues.apache.org/jira/browse/SCB-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reopened SCB-629: --- mistake status > 通过Zuul网关传递String类型的json参数，不能被正确接收 > - > > Key: SCB-629 > URL: https://issues.apache.org/jira/browse/SCB-629 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m1 >Reporter: lixing >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0 > > > 使用net.sf.json.JSONObject 发送String类型的JSONobject参数，会出现jackson > jar包报出的转换错误的Excepiton，能不能支持String类型的json参数传递，在使用zuul作为网关的时候 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-629) 通过Zuul网关传递String类型的json参数，不能被正确接收
[ https://issues.apache.org/jira/browse/SCB-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng closed SCB-629. - Resolution: Fixed use content-type "text/plain" is OK > 通过Zuul网关传递String类型的json参数，不能被正确接收 > - > > Key: SCB-629 > URL: https://issues.apache.org/jira/browse/SCB-629 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m1 >Reporter: lixing >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0 > > > 使用net.sf.json.JSONObject 发送String类型的JSONobject参数，会出现jackson > jar包报出的转换错误的Excepiton，能不能支持String类型的json参数传递，在使用zuul作为网关的时候 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-629) 通过Zuul网关传递String类型的json参数，不能被正确接收
[ https://issues.apache.org/jira/browse/SCB-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16542699#comment-16542699 ] yangyongzheng commented on SCB-629: --- I had tested if set "Content-Type" header as "text/plain" are no problem。 > 通过Zuul网关传递String类型的json参数，不能被正确接收 > - > > Key: SCB-629 > URL: https://issues.apache.org/jira/browse/SCB-629 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m1 >Reporter: lixing >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0 > > > 使用net.sf.json.JSONObject 发送String类型的JSONobject参数，会出现jackson > jar包报出的转换错误的Excepiton，能不能支持String类型的json参数传递，在使用zuul作为网关的时候 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-664) demo for integration with zuul
[ https://issues.apache.org/jira/browse/SCB-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16529307#comment-16529307 ] yangyongzheng commented on SCB-664: --- I think this : [https://github.com/zhengyangyong/gateway-perf/tree/master/zuul-service] may what you want > demo for integration with zuul > -- > > Key: SCB-664 > URL: https://issues.apache.org/jira/browse/SCB-664 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: miaoyanjie >Priority: Major > > 需要一个集成java-chassis 和 zuul做网关的demo, 或者直接做成pom包。 > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-667) gracefully shutdown is not work in some case
[ https://issues.apache.org/jira/browse/SCB-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng updated SCB-667: -- Description: In some case like consumer never stop sending request to prodiver, privider do not reject new request from consumer and still process them, So shutdown will be blocked. was: In some case like consumer never stop sending request to prodiver, privider can not shutdown and will be blocked. > gracefully shutdown is not work in some case > > > Key: SCB-667 > URL: https://issues.apache.org/jira/browse/SCB-667 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m1 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > In some case like consumer never stop sending request to prodiver, privider > do not reject new request from consumer and still process them, > So shutdown will be blocked. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-667) gracefully shutdown is not work in some case
yangyongzheng created SCB-667: - Summary: gracefully shutdown is not work in some case Key: SCB-667 URL: https://issues.apache.org/jira/browse/SCB-667 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Affects Versions: java-chassis-1.0.0-m1 Reporter: yangyongzheng Assignee: yangyongzheng Fix For: java-chassis-1.0.0-m2 In some case like consumer never stop sending request to prodiver, privider can not shutdown and will be blocked. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-659) Fix build failed in Springmvc Integration Test
[ https://issues.apache.org/jira/browse/SCB-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng resolved SCB-659. --- Resolution: Fixed > Fix build failed in Springmvc Integration Test > -- > > Key: SCB-659 > URL: https://issues.apache.org/jira/browse/SCB-659 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m1 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > springmvc-tests-common is not marked as test-jar so run "mvn clean install > -Pit" will failed because unable found this module -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-659) Fix build failed in Springmvc Integration Test
yangyongzheng created SCB-659: - Summary: Fix build failed in Springmvc Integration Test Key: SCB-659 URL: https://issues.apache.org/jira/browse/SCB-659 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Affects Versions: java-chassis-1.0.0-m1 Reporter: yangyongzheng Assignee: yangyongzheng Fix For: java-chassis-1.0.0-m2 springmvc-tests-common is not marked as test-jar so run "mvn clean install -Pit" will failed because unable found this module -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-651) QPS rate limit bug
[ https://issues.apache.org/jira/browse/SCB-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-651: - Assignee: Sean Li > QPS rate limit bug > -- > > Key: SCB-651 > URL: https://issues.apache.org/jira/browse/SCB-651 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m1 >Reporter: Sean Li >Assignee: Sean Li >Priority: Major > Attachments: limit value as 1.jpeg, limit value as 2.jpeg > > > When setting _servicecomb.flowcontrol.Provider.qps.limit.[ServiceName]_, the > actual number of requests allowed per second is always 1 less than the limit > value. > For example, if I set _flowcontrol.Provider.qps.limit._ > _business-service-consumer_ as 1, I'll get NO successful request at the very > beginning, although I would expect 1 successful request instead of none. > Similarly, if I set _flowcontrol.Provider.qps.limit._ > _business-service-consumer_ as 2, I'll get 1 successful request instead of 2. > > However, if I pause before sending requests, for example add > _Thread.sleep(100)_ before invoking the first request, the number of requests > allowed per second will be correct this time. (i.e. 1 successful request when > limit value is 1, 2 successful requests when limit value is 2, etc.) > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-650) update java chassis version in archetype from 1.0.0-m2.SNAPSHOT to 1.0.0-m1
[ https://issues.apache.org/jira/browse/SCB-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng closed SCB-650. - Resolution: Invalid > update java chassis version in archetype from 1.0.0-m2.SNAPSHOT to 1.0.0-m1 > --- > > Key: SCB-650 > URL: https://issues.apache.org/jira/browse/SCB-650 > Project: Apache ServiceComb > Issue Type: Improvement > Components: Java-Chassis >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > > Because 1.0.0-m2 have not release but we need publish article to InfoQ、CSDN > etc，we need change java chassis version in archetype from 1.0.0-m2.SNAPSHOT > to 1.0.0-m1 in order to let user build generated project successfully. > > the version will change to 1.0.0-m2 when released. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-650) update java chassis version in archetype from 1.0.0-m2.SNAPSHOT to 1.0.0-m1
yangyongzheng created SCB-650: - Summary: update java chassis version in archetype from 1.0.0-m2.SNAPSHOT to 1.0.0-m1 Key: SCB-650 URL: https://issues.apache.org/jira/browse/SCB-650 Project: Apache ServiceComb Issue Type: Improvement Components: Java-Chassis Reporter: yangyongzheng Assignee: yangyongzheng Because 1.0.0-m2 have not release but we need publish article to InfoQ、CSDN etc，we need change java chassis version in archetype from 1.0.0-m2.SNAPSHOT to 1.0.0-m1 in order to let user build generated project successfully. the version will change to 1.0.0-m2 when released. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCB-629) 通过Zuul网关传递String类型的json参数，不能被正确接收
[ https://issues.apache.org/jira/browse/SCB-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng updated SCB-629: -- Fix Version/s: Java-chassis-1.0.0 > 通过Zuul网关传递String类型的json参数，不能被正确接收 > - > > Key: SCB-629 > URL: https://issues.apache.org/jira/browse/SCB-629 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m1 >Reporter: lixing >Assignee: yangyongzheng >Priority: Major > Fix For: Java-chassis-1.0.0 > > > 使用net.sf.json.JSONObject 发送String类型的JSONobject参数，会出现jackson > jar包报出的转换错误的Excepiton，能不能支持String类型的json参数传递，在使用zuul作为网关的时候 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-633) Correct artifactId and module of saga-spring-cloud-demo
yangyongzheng created SCB-633: - Summary: Correct artifactId and module of saga-spring-cloud-demo Key: SCB-633 URL: https://issues.apache.org/jira/browse/SCB-633 Project: Apache ServiceComb Issue Type: Improvement Components: Saga Affects Versions: saga-0.2.0 Reporter: yangyongzheng Assignee: yangyongzheng Fix For: saga-0.2.0 The artifactId and module name of saga-spring-cloud-demo is not correct and make user confusing. This job had done in https://issues.apache.org/jira/browse/SCB-628 but seems imperfect -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-629) 通过Zuul网关传递String类型的json参数，不能被正确接收
[ https://issues.apache.org/jira/browse/SCB-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16497513#comment-16497513 ] yangyongzheng commented on SCB-629: --- Can you try setting 'Content-Type' as 'text/plain' to let gateway known is not necessary process body as json, may work > 通过Zuul网关传递String类型的json参数，不能被正确接收 > - > > Key: SCB-629 > URL: https://issues.apache.org/jira/browse/SCB-629 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m1 >Reporter: lixing >Assignee: yangyongzheng >Priority: Major > > 使用net.sf.json.JSONObject 发送String类型的JSONobject参数，会出现jackson > jar包报出的转换错误的Excepiton，能不能支持String类型的json参数传递，在使用zuul作为网关的时候 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-629) 通过Zuul网关传递String类型的json参数，不能被正确接收
[ https://issues.apache.org/jira/browse/SCB-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-629: - Assignee: yangyongzheng > 通过Zuul网关传递String类型的json参数，不能被正确接收 > - > > Key: SCB-629 > URL: https://issues.apache.org/jira/browse/SCB-629 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m1 >Reporter: lixing >Assignee: yangyongzheng >Priority: Major > > 使用net.sf.json.JSONObject 发送String类型的JSONobject参数，会出现jackson > jar包报出的转换错误的Excepiton，能不能支持String类型的json参数传递，在使用zuul作为网关的时候 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-562) Java Chassis will throw NPE when producer impl do not contain any method
[
https://issues.apache.org/jira/browse/SCB-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yangyongzheng resolved SCB-562.
---
Resolution: Fixed
> Java Chassis will throw NPE when producer impl do not contain any method
>
>
> Key: SCB-562
> URL: https://issues.apache.org/jira/browse/SCB-562
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Affects Versions: java-chassis-1.0.0-m1
>Reporter: yangyongzheng
>Assignee: yangyongzheng
>Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>
> If a producer impl do not contain any method like :
> ```java
> @RestSchema(schemaId = "hello")
> @Path("/")
> public class HelloImpl {
> }
> ```
> Then an NPE will throw when startup:
> 2018-05-09 08:50:04,333 [ERROR] cse init failed,
> Exception: java.lang.NullPointerException; null
> java.lang.NullPointerException
> at
> org.apache.servicecomb.swagger.generator.core.utils.ClassUtils.createInterface(ClassUtils.java:212)
> at
> org.apache.servicecomb.swagger.generator.core.utils.ClassUtils.getOrCreateInterface(ClassUtils.java:203)
> at
> org.apache.servicecomb.swagger.generator.core.utils.ClassUtils.getOrCreateInterface(ClassUtils.java:182)
> at
> org.apache.servicecomb.core.definition.schema.AbstractSchemaFactory.generateSwagger(AbstractSchemaFactory.java:112)
> at
> org.apache.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:110)
> at
> org.apache.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:47)
> at
> org.apache.servicecomb.core.definition.schema.AbstractSchemaFactory.getOrCreateSchema(AbstractSchemaFactory.java:65)
> at
> org.apache.servicecomb.core.definition.schema.ProducerSchemaFactory.getOrCreateProducerSchema(ProducerSchemaFactory.java:80)
> at
> org.apache.servicecomb.provider.rest.common.RestProducerProvider.init(RestProducerProvider.java:48)
> at
> org.apache.servicecomb.core.provider.producer.ProducerProviderManager.init(ProducerProviderManager.java:45)
> at
> org.apache.servicecomb.core.CseApplicationListener.onApplicationEvent(CseApplicationListener.java:118)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:166)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:138)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:383)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:337)
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:882)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:545)
> at
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:139)
> at
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:93)
> at
> org.apache.servicecomb.foundation.common.utils.BeanUtils.init(BeanUtils.java:37)
> at
> org.apache.servicecomb.foundation.common.utils.BeanUtils.init(BeanUtils.java:33)
> at io.demo.Application.main(Application.java:40)
>
> org.apache.servicecomb.core.CseApplicationListener.onApplicationEvent(CseApplicationListener.java:145)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SCB-610) Improvement Blog of easy-build-microservice-system-part-II
[ https://issues.apache.org/jira/browse/SCB-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493231#comment-16493231 ] yangyongzheng commented on SCB-610: --- When user need construct a user service, this step is essential. So if we want user can "5 minutes to Implement customer relationship management" , we must provide a new archetype named "user-service-archetype" to include these contents. > Improvement Blog of easy-build-microservice-system-part-II > -- > > Key: SCB-610 > URL: https://issues.apache.org/jira/browse/SCB-610 > Project: Apache ServiceComb > Issue Type: Wish > Components: website >Reporter: Zhinan Lin >Assignee: yangyongzheng >Priority: Major > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > I have gone through the Blog of easy-build-microservice-system-part-II [1], > in order to promote the community, create some improvement suggestion I > wished here. > # I find that there is no place to describe how easily can be by using > scaffold. we can describe it by comparing to the old way. For example, if we > using the old way, we should first write the POM.xml, and then , > something like this, Or the readers will get no feeling about what we want to > express. > # How about changing title of the blog to “Easy Micro Service Series: 5 > minutes to Implement customer relationship management”， in Chinese, > 轻松微服务系列：5分钟实现客户关系管理, to make title more clear and less confuse. > > [1] > [http://servicecomb.incubator.apache.org/cn/docs/easy-build-microservice-system-part-II/|http://example.com/] > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-610) Improvement Blog of easy-build-microservice-system-part-II
[ https://issues.apache.org/jira/browse/SCB-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-610: - Assignee: yangyongzheng > Improvement Blog of easy-build-microservice-system-part-II > -- > > Key: SCB-610 > URL: https://issues.apache.org/jira/browse/SCB-610 > Project: Apache ServiceComb > Issue Type: Wish > Components: website >Reporter: Zhinan Lin >Assignee: yangyongzheng >Priority: Major > Original Estimate: 0.5h > Remaining Estimate: 0.5h > > I have gone through the Blog of easy-build-microservice-system-part-II [1], > in order to promote the community, create some improvement suggestion I > wished here. > # I find that there is no place to describe how easily can be by using > scaffold. we can describe it by comparing to the old way. For example, if we > using the old way, we should first write the POM.xml, and then , > something like this, Or the readers will get no feeling about what we want to > express. > # How about changing title of the blog to “Easy Micro Service Series: 5 > minutes to Implement customer relationship management”， in Chinese, > 轻松微服务系列：5分钟实现客户关系管理, to make title more clear and less confuse. > > [1] > [http://servicecomb.incubator.apache.org/cn/docs/easy-build-microservice-system-part-II/|http://example.com/] > > > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-502) logs日志没有输出
[ https://issues.apache.org/jira/browse/SCB-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492311#comment-16492311 ] yangyongzheng commented on SCB-502: --- [~njiang], code is here [https://github.com/zhengyangyong/ServiceComb-Java-Chassis/tree/SCB-502/samples/use-log4j2-sample,] I need [~msnetc] check whether meet the requirements, then will submit PR > logs日志没有输出 > -- > > Key: SCB-502 > URL: https://issues.apache.org/jira/browse/SCB-502 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m1 >Reporter: miaoyanjie >Assignee: yangyongzheng >Priority: Major > Labels: log4j, log4j2, servicecomb > Fix For: java-chassis-1.0.0-m2 > > Original Estimate: 24h > Remaining Estimate: 24h > > 急急急 > 我项目是以springboot为基础构建的，用Log4j2输出日志成功。 > 加上servicecomb之后，日志没有输出。 > 并且incubator-servicecomb-java-chassis/samples/bmi的日志也没有输出成功。 > 希望给出解决方案。 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 ] yangyongzheng updated SCB-592: -- Fix Version/s: (was: java-chassis-1.0.0-m2) Java-chassis-1.0.0 > Spring Zuul Tracing Integration Tests CI failed > --- > > Key: SCB-592 > URL: https://issues.apache.org/jira/browse/SCB-592 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: Java-chassis-1.0.0 > > > Spring Zuul Tracing Integration Tests is easy failed by : > *Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on > project spring-zuul-tracing-tests Execution* > *Exception Error occurred in starting fork, check output in log* > > we need fix it -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-592) Spring Zuul Tracing Integration Tests CI failed
[ https://issues.apache.org/jira/browse/SCB-592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492302#comment-16492302 ] yangyongzheng commented on SCB-592: --- this task delay to 1.0.0 > Spring Zuul Tracing Integration Tests CI failed > --- > > Key: SCB-592 > URL: https://issues.apache.org/jira/browse/SCB-592 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: Java-chassis-1.0.0 > > > Spring Zuul Tracing Integration Tests is easy failed by : > *Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on > project spring-zuul-tracing-tests Execution* > *Exception Error occurred in starting fork, check output in log* > > we need fix it -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-69) Provide MicroService project scaffold as JHipster does
[ https://issues.apache.org/jira/browse/SCB-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-69: Assignee: (was: yangyongzheng) > Provide MicroService project scaffold as JHipster does > -- > > Key: SCB-69 > URL: https://issues.apache.org/jira/browse/SCB-69 > Project: Apache ServiceComb > Issue Type: Wish > Components: Java-Chassis >Reporter: Bo Li >Priority: Major > Labels: roadmap > > ServiceComb是否有一个类似于JHipster这样包含完整的脚手架功能的微服务构建工具， > 尤其是针对典型的应用场景，对企业应用开发用户来说透明，直接通过脚手架或者插件进行配置和构建，只要关注业务开发就好了。 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-502) logs日志没有输出
[ https://issues.apache.org/jira/browse/SCB-502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492217#comment-16492217 ] yangyongzheng commented on SCB-502: --- I will add a sample of how to use log4j2 as log implemention > logs日志没有输出 > -- > > Key: SCB-502 > URL: https://issues.apache.org/jira/browse/SCB-502 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m1 >Reporter: miaoyanjie >Assignee: yangyongzheng >Priority: Major > Labels: log4j, log4j2, servicecomb > Fix For: java-chassis-1.0.0-m2 > > Original Estimate: 24h > Remaining Estimate: 24h > > 急急急 > 我项目是以springboot为基础构建的，用Log4j2输出日志成功。 > 加上servicecomb之后，日志没有输出。 > 并且incubator-servicecomb-java-chassis/samples/bmi的日志也没有输出成功。 > 希望给出解决方案。 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-69) Provide MicroService project scaffold as JHipster does
[ https://issues.apache.org/jira/browse/SCB-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492213#comment-16492213 ] yangyongzheng commented on SCB-69: -- we will extend from spring initializ like dubbo > Provide MicroService project scaffold as JHipster does > -- > > Key: SCB-69 > URL: https://issues.apache.org/jira/browse/SCB-69 > Project: Apache ServiceComb > Issue Type: Wish > Components: Java-Chassis >Reporter: Bo Li >Assignee: yangyongzheng >Priority: Major > Labels: roadmap > > ServiceComb是否有一个类似于JHipster这样包含完整的脚手架功能的微服务构建工具， > 尤其是针对典型的应用场景，对企业应用开发用户来说透明，直接通过脚手架或者插件进行配置和构建，只要关注业务开发就好了。 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 ] yangyongzheng updated SCB-592: -- Description: Spring Zuul Tracing Integration Tests is easy failed by : *Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project spring-zuul-tracing-tests Execution* *Exception Error occurred in starting fork, check output in log* we need fix it was: Spring Zuul Tracing Integration Tests is easy failed by : Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project spring-zuul-tracing-tests Execution Exception Error occurred in starting fork, check output in log we need fix it > Spring Zuul Tracing Integration Tests CI failed > --- > > Key: SCB-592 > URL: https://issues.apache.org/jira/browse/SCB-592 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > Spring Zuul Tracing Integration Tests is easy failed by : > *Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on > project spring-zuul-tracing-tests Execution* > *Exception Error occurred in starting fork, check output in log* > > we need fix it -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[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 ] yangyongzheng updated SCB-592: -- Description: Spring Zuul Tracing Integration Tests is easy failed by : Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project spring-zuul-tracing-tests Execution Exception Error occurred in starting fork, check output in log we need fix it was: Spring Zuul Tracing Integration Tests is easy failed by : Failed to execute goal [32morg.apache.maven.plugins:maven-surefire-plugin:2.19.1:test[m [1m(default-test)[m on project [36mspring-zuul-tracing-tests[m: [1;31mExecutionException Error occurred in starting fork, check output in log[m -> [1m[Help 1][m we need fix it > Spring Zuul Tracing Integration Tests CI failed > --- > > Key: SCB-592 > URL: https://issues.apache.org/jira/browse/SCB-592 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > Spring Zuul Tracing Integration Tests is easy failed by : > Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on > project spring-zuul-tracing-tests Execution > Exception Error occurred in starting fork, check output in log > > we need fix it -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (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 ] yangyongzheng reassigned SCB-592: - Assignee: yangyongzheng > Spring Zuul Tracing Integration Tests CI failed > --- > > Key: SCB-592 > URL: https://issues.apache.org/jira/browse/SCB-592 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > Spring Zuul Tracing Integration Tests is easy failed by : > Failed to execute goal > [32morg.apache.maven.plugins:maven-surefire-plugin:2.19.1:test[m > [1m(default-test)[m on project [36mspring-zuul-tracing-tests[m: > [1;31mExecutionException Error occurred in starting fork, check output in > log[m -> [1m[Help 1][m > > we need fix it -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-69) Provide MicroService project scaffold as JHipster does
[ https://issues.apache.org/jira/browse/SCB-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483399#comment-16483399 ] yangyongzheng commented on SCB-69: -- it seems provided a generator for user to use ui mode create proejct with microservice features selected. [https://start.jhipster.tech/#/generate-application] we may do same thing > Provide MicroService project scaffold as JHipster does > -- > > Key: SCB-69 > URL: https://issues.apache.org/jira/browse/SCB-69 > Project: Apache ServiceComb > Issue Type: Wish > Components: Java-Chassis >Reporter: Bo Li >Assignee: yangyongzheng >Priority: Major > Labels: roadmap > > ServiceComb是否有一个类似于JHipster这样包含完整的脚手架功能的微服务构建工具， > 尤其是针对典型的应用场景，对企业应用开发用户来说透明，直接通过脚手架或者插件进行配置和构建，只要关注业务开发就好了。 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-597) update spring boot version from 1.4.5 to 1.5.12 in starter archetype
[ https://issues.apache.org/jira/browse/SCB-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng resolved SCB-597. --- Resolution: Fixed > update spring boot version from 1.4.5 to 1.5.12 in starter archetype > > > Key: SCB-597 > URL: https://issues.apache.org/jira/browse/SCB-597 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > Need update spring boot version from 1.4.5 to 1.5.12 in > [business-service-spring-boot-starter|https://github.com/apache/incubator-servicecomb-java-chassis/tree/master/archetypes/business-service-spring-boot-starter] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-502) logs日志没有输出
[ https://issues.apache.org/jira/browse/SCB-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-502: - Assignee: yangyongzheng > logs日志没有输出 > -- > > Key: SCB-502 > URL: https://issues.apache.org/jira/browse/SCB-502 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m1 >Reporter: miaoyanjie >Assignee: yangyongzheng >Priority: Major > Labels: log4j, log4j2, servicecomb > Fix For: java-chassis-1.0.0-m2 > > Original Estimate: 24h > Remaining Estimate: 24h > > 急急急 > 我项目是以springboot为基础构建的，用Log4j2输出日志成功。 > 加上servicecomb之后，日志没有输出。 > 并且incubator-servicecomb-java-chassis/samples/bmi的日志也没有输出成功。 > 希望给出解决方案。 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-69) Provide MicroService project scaffold as JHipster does
[ https://issues.apache.org/jira/browse/SCB-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483286#comment-16483286 ] yangyongzheng commented on SCB-69: -- I will take a look at what is the JHipster > Provide MicroService project scaffold as JHipster does > -- > > Key: SCB-69 > URL: https://issues.apache.org/jira/browse/SCB-69 > Project: Apache ServiceComb > Issue Type: Wish > Components: Java-Chassis >Reporter: Bo Li >Assignee: yangyongzheng >Priority: Major > Labels: roadmap > > ServiceComb是否有一个类似于JHipster这样包含完整的脚手架功能的微服务构建工具， > 尤其是针对典型的应用场景，对企业应用开发用户来说透明，直接通过脚手架或者插件进行配置和构建，只要关注业务开发就好了。 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-597) update spring boot version from 1.4.5 to 1.5.12 in starter archetype
yangyongzheng created SCB-597: - Summary: update spring boot version from 1.4.5 to 1.5.12 in starter archetype Key: SCB-597 URL: https://issues.apache.org/jira/browse/SCB-597 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Affects Versions: java-chassis-1.0.0-m2 Reporter: yangyongzheng Assignee: yangyongzheng Fix For: java-chassis-1.0.0-m2 Need update spring boot version from 1.4.5 to 1.5.12 in [business-service-spring-boot-starter|https://github.com/apache/incubator-servicecomb-java-chassis/tree/master/archetypes/business-service-spring-boot-starter] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-587) Fix archetypes readme
[
https://issues.apache.org/jira/browse/SCB-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yangyongzheng resolved SCB-587.
---
Resolution: Fixed
> Fix archetypes readme
> -
>
> Key: SCB-587
> URL: https://issues.apache.org/jira/browse/SCB-587
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Affects Versions: java-chassis-1.0.0-m2
>Reporter: yangyongzheng
>Assignee: yangyongzheng
>Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>
> In archetype readme.md,generate from SNAPSHOT repo command is :
> mvn archetype:generate -DarchetypeGroupId=org.apache.servicecomb.archetypes
> -DarchetypeArtifactId=business-service-jaxrs-archetype
> -DarchetypeVersion=${archetype-version}
> -DarchetypeRepository=[https://repository.apache.org/content/groups/snapshots-group]
>
> if version of archetype plugin is 3.0+, archetypeRepository had
> deleted,[https://maven.apache.org/archetype/maven-archetype-plugin/generate-mojo.html]
> We need replace it with :
> mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate
> -DarchetypeGroupId=org.apache.servicecomb.archetypes
> -DarchetypeArtifactId=business-service-jaxrs-archetype
> -DarchetypeVersion=1.0.0-m2-SNAPSHOT
> -DarchetypeRepository=https://repository.apache.org/content/groups/snapshots-group
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SCB-588) Set archetypes sourceEncoding to UTF-8
[ https://issues.apache.org/jira/browse/SCB-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng resolved SCB-588. --- Resolution: Fixed > Set archetypes sourceEncoding to UTF-8 > -- > > Key: SCB-588 > URL: https://issues.apache.org/jira/browse/SCB-588 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > Need set archetypes sourceEncoding to utf-8,not follow system default encoding > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-548) Support Gracefully Shutdown
[
https://issues.apache.org/jira/browse/SCB-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yangyongzheng resolved SCB-548.
---
Resolution: Fixed
> Support Gracefully Shutdown
> ---
>
> Key: SCB-548
> URL: https://issues.apache.org/jira/browse/SCB-548
> Project: Apache ServiceComb
> Issue Type: Improvement
> Components: Java-Chassis
>Affects Versions: java-chassis-1.0.0-m2
>Reporter: yangyongzheng
>Assignee: yangyongzheng
>Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>
> We did not implement gracefully shutdown yet:
> ```java
> // 当程序退出时，进行相关清理，注意：kill -9 {pid}下无效
> // 1. 去注册实例信息
> // TODO 服务优雅退出
> if (applicationContext instanceof AbstractApplicationContext) {
> ((AbstractApplicationContext)
> applicationContext).registerShutdownHook();
> }
> ```
>
> And had got an issue :
> https://github.com/apache/incubator-servicecomb-java-chassis/issues/685 from
> user.
> So it's time we must do it and remove this TODO
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SCB-592) Spring Zuul Tracing Integration Tests CI failed
yangyongzheng created SCB-592: - Summary: Spring Zuul Tracing Integration Tests CI failed Key: SCB-592 URL: https://issues.apache.org/jira/browse/SCB-592 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Affects Versions: java-chassis-1.0.0-m2 Reporter: yangyongzheng Fix For: java-chassis-1.0.0-m2 Spring Zuul Tracing Integration Tests is easy failed by : Failed to execute goal [32morg.apache.maven.plugins:maven-surefire-plugin:2.19.1:test[m [1m(default-test)[m on project [36mspring-zuul-tracing-tests[m: [1;31mExecutionException Error occurred in starting fork, check output in log[m -> [1m[Help 1][m we need fix it -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-562) Java Chassis will throw NPE when producer impl do not contain any method
[
https://issues.apache.org/jira/browse/SCB-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yangyongzheng reassigned SCB-562:
-
Assignee: yangyongzheng
> Java Chassis will throw NPE when producer impl do not contain any method
>
>
> Key: SCB-562
> URL: https://issues.apache.org/jira/browse/SCB-562
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Affects Versions: java-chassis-1.0.0-m1
>Reporter: yangyongzheng
>Assignee: yangyongzheng
>Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>
> If a producer impl do not contain any method like :
> ```java
> @RestSchema(schemaId = "hello")
> @Path("/")
> public class HelloImpl {
> }
> ```
> Then an NPE will throw when startup:
> 2018-05-09 08:50:04,333 [ERROR] cse init failed,
> Exception: java.lang.NullPointerException; null
> java.lang.NullPointerException
> at
> org.apache.servicecomb.swagger.generator.core.utils.ClassUtils.createInterface(ClassUtils.java:212)
> at
> org.apache.servicecomb.swagger.generator.core.utils.ClassUtils.getOrCreateInterface(ClassUtils.java:203)
> at
> org.apache.servicecomb.swagger.generator.core.utils.ClassUtils.getOrCreateInterface(ClassUtils.java:182)
> at
> org.apache.servicecomb.core.definition.schema.AbstractSchemaFactory.generateSwagger(AbstractSchemaFactory.java:112)
> at
> org.apache.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:110)
> at
> org.apache.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:47)
> at
> org.apache.servicecomb.core.definition.schema.AbstractSchemaFactory.getOrCreateSchema(AbstractSchemaFactory.java:65)
> at
> org.apache.servicecomb.core.definition.schema.ProducerSchemaFactory.getOrCreateProducerSchema(ProducerSchemaFactory.java:80)
> at
> org.apache.servicecomb.provider.rest.common.RestProducerProvider.init(RestProducerProvider.java:48)
> at
> org.apache.servicecomb.core.provider.producer.ProducerProviderManager.init(ProducerProviderManager.java:45)
> at
> org.apache.servicecomb.core.CseApplicationListener.onApplicationEvent(CseApplicationListener.java:118)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:166)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:138)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:383)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:337)
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:882)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:545)
> at
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:139)
> at
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:93)
> at
> org.apache.servicecomb.foundation.common.utils.BeanUtils.init(BeanUtils.java:37)
> at
> org.apache.servicecomb.foundation.common.utils.BeanUtils.init(BeanUtils.java:33)
> at io.demo.Application.main(Application.java:40)
>
> org.apache.servicecomb.core.CseApplicationListener.onApplicationEvent(CseApplicationListener.java:145)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SCB-588) Set archetypes sourceEncoding to UTF-8
yangyongzheng created SCB-588: - Summary: Set archetypes sourceEncoding to UTF-8 Key: SCB-588 URL: https://issues.apache.org/jira/browse/SCB-588 Project: Apache ServiceComb Issue Type: Bug Components: Java-Chassis Affects Versions: java-chassis-1.0.0-m2 Reporter: yangyongzheng Assignee: yangyongzheng Fix For: java-chassis-1.0.0-m2 Need set archetypes sourceEncoding to utf-8,not follow system default encoding -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-587) Fix archetypes readme
yangyongzheng created SCB-587:
-
Summary: Fix archetypes readme
Key: SCB-587
URL: https://issues.apache.org/jira/browse/SCB-587
Project: Apache ServiceComb
Issue Type: Bug
Components: Java-Chassis
Affects Versions: java-chassis-1.0.0-m2
Reporter: yangyongzheng
Assignee: yangyongzheng
Fix For: java-chassis-1.0.0-m2
In archetype readme.md,generate from SNAPSHOT repo command is :
mvn archetype:generate -DarchetypeGroupId=org.apache.servicecomb.archetypes
-DarchetypeArtifactId=business-service-jaxrs-archetype
-DarchetypeVersion=${archetype-version}
-DarchetypeRepository=[https://repository.apache.org/content/groups/snapshots-group]
if version of archetype plugin is 3.0+, archetypeRepository had
deleted,[https://maven.apache.org/archetype/maven-archetype-plugin/generate-mojo.html]
We need replace it with :
mvn org.apache.maven.plugins:maven-archetype-plugin:2.4:generate
-DarchetypeGroupId=org.apache.servicecomb.archetypes
-DarchetypeArtifactId=business-service-jaxrs-archetype
-DarchetypeVersion=1.0.0-m2-SNAPSHOT
-DarchetypeRepository=https://repository.apache.org/content/groups/snapshots-group
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SCB-562) Java Chassis will throw NPE when producer impl do not contain any method
[
https://issues.apache.org/jira/browse/SCB-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468321#comment-16468321
]
yangyongzheng commented on SCB-562:
---
He may fill it later, and NPE is so unfriendly, our user had done this ...
> Java Chassis will throw NPE when producer impl do not contain any method
>
>
> Key: SCB-562
> URL: https://issues.apache.org/jira/browse/SCB-562
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Affects Versions: java-chassis-1.0.0-m1
>Reporter: yangyongzheng
>Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>
> If a producer impl do not contain any method like :
> ```java
> @RestSchema(schemaId = "hello")
> @Path("/")
> public class HelloImpl {
> }
> ```
> Then an NPE will throw when startup:
> 2018-05-09 08:50:04,333 [ERROR] cse init failed,
> Exception: java.lang.NullPointerException; null
> java.lang.NullPointerException
> at
> org.apache.servicecomb.swagger.generator.core.utils.ClassUtils.createInterface(ClassUtils.java:212)
> at
> org.apache.servicecomb.swagger.generator.core.utils.ClassUtils.getOrCreateInterface(ClassUtils.java:203)
> at
> org.apache.servicecomb.swagger.generator.core.utils.ClassUtils.getOrCreateInterface(ClassUtils.java:182)
> at
> org.apache.servicecomb.core.definition.schema.AbstractSchemaFactory.generateSwagger(AbstractSchemaFactory.java:112)
> at
> org.apache.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:110)
> at
> org.apache.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:47)
> at
> org.apache.servicecomb.core.definition.schema.AbstractSchemaFactory.getOrCreateSchema(AbstractSchemaFactory.java:65)
> at
> org.apache.servicecomb.core.definition.schema.ProducerSchemaFactory.getOrCreateProducerSchema(ProducerSchemaFactory.java:80)
> at
> org.apache.servicecomb.provider.rest.common.RestProducerProvider.init(RestProducerProvider.java:48)
> at
> org.apache.servicecomb.core.provider.producer.ProducerProviderManager.init(ProducerProviderManager.java:45)
> at
> org.apache.servicecomb.core.CseApplicationListener.onApplicationEvent(CseApplicationListener.java:118)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:166)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:138)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:383)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:337)
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:882)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:545)
> at
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:139)
> at
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:93)
> at
> org.apache.servicecomb.foundation.common.utils.BeanUtils.init(BeanUtils.java:37)
> at
> org.apache.servicecomb.foundation.common.utils.BeanUtils.init(BeanUtils.java:33)
> at io.demo.Application.main(Application.java:40)
>
> org.apache.servicecomb.core.CseApplicationListener.onApplicationEvent(CseApplicationListener.java:145)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SCB-562) Java Chassis will throw NPE when producer impl do not contain any method
[
https://issues.apache.org/jira/browse/SCB-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16468189#comment-16468189
]
yangyongzheng commented on SCB-562:
---
I think unpublish this service impl is a good idea
> Java Chassis will throw NPE when producer impl do not contain any method
>
>
> Key: SCB-562
> URL: https://issues.apache.org/jira/browse/SCB-562
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Affects Versions: java-chassis-1.0.0-m1
>Reporter: yangyongzheng
>Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>
> If a producer impl do not contain any method like :
> ```java
> @RestSchema(schemaId = "hello")
> @Path("/")
> public class HelloImpl {
> }
> ```
> Then an NPE will throw when startup:
> 2018-05-09 08:50:04,333 [ERROR] cse init failed,
> Exception: java.lang.NullPointerException; null
> java.lang.NullPointerException
> at
> org.apache.servicecomb.swagger.generator.core.utils.ClassUtils.createInterface(ClassUtils.java:212)
> at
> org.apache.servicecomb.swagger.generator.core.utils.ClassUtils.getOrCreateInterface(ClassUtils.java:203)
> at
> org.apache.servicecomb.swagger.generator.core.utils.ClassUtils.getOrCreateInterface(ClassUtils.java:182)
> at
> org.apache.servicecomb.core.definition.schema.AbstractSchemaFactory.generateSwagger(AbstractSchemaFactory.java:112)
> at
> org.apache.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:110)
> at
> org.apache.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:47)
> at
> org.apache.servicecomb.core.definition.schema.AbstractSchemaFactory.getOrCreateSchema(AbstractSchemaFactory.java:65)
> at
> org.apache.servicecomb.core.definition.schema.ProducerSchemaFactory.getOrCreateProducerSchema(ProducerSchemaFactory.java:80)
> at
> org.apache.servicecomb.provider.rest.common.RestProducerProvider.init(RestProducerProvider.java:48)
> at
> org.apache.servicecomb.core.provider.producer.ProducerProviderManager.init(ProducerProviderManager.java:45)
> at
> org.apache.servicecomb.core.CseApplicationListener.onApplicationEvent(CseApplicationListener.java:118)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:166)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:138)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:383)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:337)
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:882)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:545)
> at
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:139)
> at
> org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:93)
> at
> org.apache.servicecomb.foundation.common.utils.BeanUtils.init(BeanUtils.java:37)
> at
> org.apache.servicecomb.foundation.common.utils.BeanUtils.init(BeanUtils.java:33)
> at io.demo.Application.main(Application.java:40)
>
> org.apache.servicecomb.core.CseApplicationListener.onApplicationEvent(CseApplicationListener.java:145)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SCB-562) Java Chassis will throw NPE when producer impl do not contain any method
yangyongzheng created SCB-562:
-
Summary: Java Chassis will throw NPE when producer impl do not
contain any method
Key: SCB-562
URL: https://issues.apache.org/jira/browse/SCB-562
Project: Apache ServiceComb
Issue Type: Bug
Components: Java-Chassis
Affects Versions: java-chassis-1.0.0-m1
Reporter: yangyongzheng
Fix For: java-chassis-1.0.0-m2
If a producer impl do not contain any method like :
```java
@RestSchema(schemaId = "hello")
@Path("/")
public class HelloImpl {
}
```
Then an NPE will throw when startup:
2018-05-09 08:50:04,333 [ERROR] cse init failed,
Exception: java.lang.NullPointerException; null
java.lang.NullPointerException
at
org.apache.servicecomb.swagger.generator.core.utils.ClassUtils.createInterface(ClassUtils.java:212)
at
org.apache.servicecomb.swagger.generator.core.utils.ClassUtils.getOrCreateInterface(ClassUtils.java:203)
at
org.apache.servicecomb.swagger.generator.core.utils.ClassUtils.getOrCreateInterface(ClassUtils.java:182)
at
org.apache.servicecomb.core.definition.schema.AbstractSchemaFactory.generateSwagger(AbstractSchemaFactory.java:112)
at
org.apache.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:110)
at
org.apache.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:47)
at
org.apache.servicecomb.core.definition.schema.AbstractSchemaFactory.getOrCreateSchema(AbstractSchemaFactory.java:65)
at
org.apache.servicecomb.core.definition.schema.ProducerSchemaFactory.getOrCreateProducerSchema(ProducerSchemaFactory.java:80)
at
org.apache.servicecomb.provider.rest.common.RestProducerProvider.init(RestProducerProvider.java:48)
at
org.apache.servicecomb.core.provider.producer.ProducerProviderManager.init(ProducerProviderManager.java:45)
at
org.apache.servicecomb.core.CseApplicationListener.onApplicationEvent(CseApplicationListener.java:118)
at
org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:166)
at
org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:138)
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:383)
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:337)
at
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:882)
at
org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:545)
at
org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:139)
at
org.springframework.context.support.ClassPathXmlApplicationContext.(ClassPathXmlApplicationContext.java:93)
at
org.apache.servicecomb.foundation.common.utils.BeanUtils.init(BeanUtils.java:37)
at
org.apache.servicecomb.foundation.common.utils.BeanUtils.init(BeanUtils.java:33)
at io.demo.Application.main(Application.java:40)
org.apache.servicecomb.core.CseApplicationListener.onApplicationEvent(CseApplicationListener.java:145)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SCB-439) Provide Maven Archetypes in Java Chassis
[
https://issues.apache.org/jira/browse/SCB-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yangyongzheng resolved SCB-439.
---
Resolution: Fixed
> Provide Maven Archetypes in Java Chassis
>
>
> Key: SCB-439
> URL: https://issues.apache.org/jira/browse/SCB-439
> Project: Apache ServiceComb
> Issue Type: New Feature
> Components: Java-Chassis
>Affects Versions: java-chassis-1.0.0-m2
>Reporter: yangyongzheng
>Assignee: yangyongzheng
>Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>
> *What's maven archetypes ?*
> [http://maven.apache.org/guides/introduction/introduction-to-archetypes.html]
> *Why we need provide archetypes ?*
> If user create a blank maven project and want import chassis, he must do
> these steps:
> # Our chassis support multi provider and transport, also support integration
> with spring boot, he must copy right dependencies into pom, and let
> "java-chassis-dependencies" manage versions.
> # He must create "microservice.yaml" in resources folder and fill right
> setting, so I think he will copy from samples.
> # He may copy endpoint implement and replace the operations for faster
> rewrite.
> So, I think if we need write long user guide
> ([http://servicecomb.incubator.apache.org/users/]) to explain how to do,why
> don't we just create one with a "hello world" provider, then Fire.
> *What we will provide ?*
> 1.business-service-pojo
> Archetype for create a common microservice using pojo provider.
> 2.business-service-springmvc
> Archetype for create a common microservice using springmvc provider.
> 3.business-service-jaxrs
> Archetype for create a common microservice using jaxrs provider.
> 4.business-service-with-spring-boot-starter
> Archetype for create a common microservice using
> spring-boot-starter-provider.
> 5.edge-service
> Archetype for create an edge microservice using servicecomb
> edge-core with a general router dispatcher.
> 6.edge-service-with-zuul
> Archetype for create an edge microservice using spring cloud zuul.
> 7.auth-service
> Archetype for create an auth microservice with a simple jwt(Json
> Web Token) authentication.
> *How these* *archetypes build and publish* *?*
> We will buid this archetypes via _*mvn archetype:create-from-project.*_
> Then publish them into maven center repository
> ```xml
> {{org.apache.servicecomb.archetypes}}
> {{${archetype-name}}}
> {{${archetype-version}}}
> ```
> *How to use these* *archetypes generate project(module) ?*
> create project(module) via IDE, or run command :
> ```bash
> mvn archetype:generate -DarchetypeGroupId=org.apache.servicecomb.archetypes
> -DarchetypeArtifactId=business-service-xxx-archetype
> -DarchetypeVersion=${archetype-version}
> ```
> *Discussion mail :*
> [https://lists.apache.org/thread.html/15273af2af376e3d3000aa8864acfaee07c8ce08b927a3f9f8a7409d@%3Cdev.servicecomb.apache.org%3E]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SCB-439) Provide Maven Archetypes in Java Chassis
[
https://issues.apache.org/jira/browse/SCB-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467125#comment-16467125
]
yangyongzheng commented on SCB-439:
---
5.edge-service
6.edge-service-with-zuul
7.auth-service
We may provide them later
> Provide Maven Archetypes in Java Chassis
>
>
> Key: SCB-439
> URL: https://issues.apache.org/jira/browse/SCB-439
> Project: Apache ServiceComb
> Issue Type: New Feature
> Components: Java-Chassis
>Affects Versions: java-chassis-1.0.0-m2
>Reporter: yangyongzheng
>Assignee: yangyongzheng
>Priority: Major
> Fix For: java-chassis-1.0.0-m2
>
>
> *What's maven archetypes ?*
> [http://maven.apache.org/guides/introduction/introduction-to-archetypes.html]
> *Why we need provide archetypes ?*
> If user create a blank maven project and want import chassis, he must do
> these steps:
> # Our chassis support multi provider and transport, also support integration
> with spring boot, he must copy right dependencies into pom, and let
> "java-chassis-dependencies" manage versions.
> # He must create "microservice.yaml" in resources folder and fill right
> setting, so I think he will copy from samples.
> # He may copy endpoint implement and replace the operations for faster
> rewrite.
> So, I think if we need write long user guide
> ([http://servicecomb.incubator.apache.org/users/]) to explain how to do,why
> don't we just create one with a "hello world" provider, then Fire.
> *What we will provide ?*
> 1.business-service-pojo
> Archetype for create a common microservice using pojo provider.
> 2.business-service-springmvc
> Archetype for create a common microservice using springmvc provider.
> 3.business-service-jaxrs
> Archetype for create a common microservice using jaxrs provider.
> 4.business-service-with-spring-boot-starter
> Archetype for create a common microservice using
> spring-boot-starter-provider.
> 5.edge-service
> Archetype for create an edge microservice using servicecomb
> edge-core with a general router dispatcher.
> 6.edge-service-with-zuul
> Archetype for create an edge microservice using spring cloud zuul.
> 7.auth-service
> Archetype for create an auth microservice with a simple jwt(Json
> Web Token) authentication.
> *How these* *archetypes build and publish* *?*
> We will buid this archetypes via _*mvn archetype:create-from-project.*_
> Then publish them into maven center repository
> ```xml
> {{org.apache.servicecomb.archetypes}}
> {{${archetype-name}}}
> {{${archetype-version}}}
> ```
> *How to use these* *archetypes generate project(module) ?*
> create project(module) via IDE, or run command :
> ```bash
> mvn archetype:generate -DarchetypeGroupId=org.apache.servicecomb.archetypes
> -DarchetypeArtifactId=business-service-xxx-archetype
> -DarchetypeVersion=${archetype-version}
> ```
> *Discussion mail :*
> [https://lists.apache.org/thread.html/15273af2af376e3d3000aa8864acfaee07c8ce08b927a3f9f8a7409d@%3Cdev.servicecomb.apache.org%3E]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SCB-504) Upgrade to Spring boot 1.5.12.RELEASE
[ https://issues.apache.org/jira/browse/SCB-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng resolved SCB-504. --- Resolution: Fixed > Upgrade to Spring boot 1.5.12.RELEASE > - > > Key: SCB-504 > URL: https://issues.apache.org/jira/browse/SCB-504 > Project: Apache ServiceComb > Issue Type: Wish > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > https://github.com/apache/incubator-servicecomb-java-chassis/issues/654 > we may test upgrade to 1.5.12.RELEASE -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-495) Compile java-chassis 1.0.0-m2-SNAPSHOT failed
[ https://issues.apache.org/jira/browse/SCB-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng reassigned SCB-495: - Assignee: yangyongzheng > Compile java-chassis 1.0.0-m2-SNAPSHOT failed > - > > Key: SCB-495 > URL: https://issues.apache.org/jira/browse/SCB-495 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: mabin >Assignee: yangyongzheng >Priority: Major > Attachments: errorlog.txt > > > [^errorlog.txt] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-495) Compile java-chassis 1.0.0-m2-SNAPSHOT failed
[ https://issues.apache.org/jira/browse/SCB-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467081#comment-16467081 ] yangyongzheng commented on SCB-495: --- This PR had merged ,[~Mabingo] please check if fixed > Compile java-chassis 1.0.0-m2-SNAPSHOT failed > - > > Key: SCB-495 > URL: https://issues.apache.org/jira/browse/SCB-495 > Project: Apache ServiceComb > Issue Type: Bug > Components: Java-Chassis >Reporter: mabin >Priority: Major > Attachments: errorlog.txt > > > [^errorlog.txt] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-559) Instances count that show in Service Center frontend is incorrect
yangyongzheng created SCB-559: - Summary: Instances count that show in Service Center frontend is incorrect Key: SCB-559 URL: https://issues.apache.org/jira/browse/SCB-559 Project: Apache ServiceComb Issue Type: Improvement Components: Service-Center Affects Versions: service-center-1.0.0-m1 Reporter: yangyongzheng Fix For: service-center-1.0.0-m2 Instances count that show in Service Center frontend does a decrease after abount 80 second since "[INFO] Unregister microservice instance success. " had printed in java chassis,not immediately -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-540) Delete archetypes from java-chassis-dependencies
[ https://issues.apache.org/jira/browse/SCB-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng resolved SCB-540. --- Resolution: Fixed > Delete archetypes from java-chassis-dependencies > > > Key: SCB-540 > URL: https://issues.apache.org/jira/browse/SCB-540 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > It's a mistake that is unnecessary for add archetypes into > java-chassis-dependencies, we need delete them. > ```xml > > org.apache.servicecomb.archetypes > business-service-jaxrs-archetype > 1.0.0-m2-SNAPSHOT > > > org.apache.servicecomb.archetypes > business-service-pojo-archetype > 1.0.0-m2-SNAPSHOT > > > org.apache.servicecomb.archetypes > business-service-springmvc-archetype > 1.0.0-m2-SNAPSHOT > > > org.apache.servicecomb.archetypes > > business-service-spring-boot-starter-archetype > 1.0.0-m2-SNAPSHOT > > ``` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCB-548) Support Gracefully Shutdown
[
https://issues.apache.org/jira/browse/SCB-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
yangyongzheng reassigned SCB-548:
-
Assignee: yangyongzheng
> Support Gracefully Shutdown
> ---
>
> Key: SCB-548
> URL: https://issues.apache.org/jira/browse/SCB-548
> Project: Apache ServiceComb
> Issue Type: Improvement
> Components: Java-Chassis
>Affects Versions: java-chassis-1.0.0-m2
>Reporter: yangyongzheng
>Assignee: yangyongzheng
>Priority: Major
>
> We did not implement gracefully shutdown yet:
> ```java
> // 当程序退出时，进行相关清理，注意：kill -9 {pid}下无效
> // 1. 去注册实例信息
> // TODO 服务优雅退出
> if (applicationContext instanceof AbstractApplicationContext) {
> ((AbstractApplicationContext)
> applicationContext).registerShutdownHook();
> }
> ```
>
> And had got an issue :
> https://github.com/apache/incubator-servicecomb-java-chassis/issues/685 from
> user.
> So it's time we must do it and remove this TODO
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SCB-548) Support Gracefully Shutdown
yangyongzheng created SCB-548:
-
Summary: Support Gracefully Shutdown
Key: SCB-548
URL: https://issues.apache.org/jira/browse/SCB-548
Project: Apache ServiceComb
Issue Type: Improvement
Components: Java-Chassis
Affects Versions: java-chassis-1.0.0-m2
Reporter: yangyongzheng
We did not implement gracefully shutdown yet:
```java
// 当程序退出时，进行相关清理，注意：kill -9 {pid}下无效
// 1. 去注册实例信息
// TODO 服务优雅退出
if (applicationContext instanceof AbstractApplicationContext) {
((AbstractApplicationContext)
applicationContext).registerShutdownHook();
}
```
And had got an issue :
https://github.com/apache/incubator-servicecomb-java-chassis/issues/685 from
user.
So it's time we must do it and remove this TODO
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SCB-540) Delete archetypes from java-chassis-dependencies
[ https://issues.apache.org/jira/browse/SCB-540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng updated SCB-540: -- Description: It's a mistake that is unnecessary for add archetypes into java-chassis-dependencies, we need delete them. ```xml org.apache.servicecomb.archetypes business-service-jaxrs-archetype 1.0.0-m2-SNAPSHOT org.apache.servicecomb.archetypes business-service-pojo-archetype 1.0.0-m2-SNAPSHOT org.apache.servicecomb.archetypes business-service-springmvc-archetype 1.0.0-m2-SNAPSHOT org.apache.servicecomb.archetypes business-service-spring-boot-starter-archetype 1.0.0-m2-SNAPSHOT ``` was:It's a mistake that is unnecessary for add archetypes into java-chassis-dependencies, we need delete them. > Delete archetypes from java-chassis-dependencies > > > Key: SCB-540 > URL: https://issues.apache.org/jira/browse/SCB-540 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > It's a mistake that is unnecessary for add archetypes into > java-chassis-dependencies, we need delete them. > ```xml > > org.apache.servicecomb.archetypes > business-service-jaxrs-archetype > 1.0.0-m2-SNAPSHOT > > > org.apache.servicecomb.archetypes > business-service-pojo-archetype > 1.0.0-m2-SNAPSHOT > > > org.apache.servicecomb.archetypes > business-service-springmvc-archetype > 1.0.0-m2-SNAPSHOT > > > org.apache.servicecomb.archetypes > > business-service-spring-boot-starter-archetype > 1.0.0-m2-SNAPSHOT > > ``` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SCB-540) Delete archetypes from java-chassis-dependencies
yangyongzheng created SCB-540: - Summary: Delete archetypes from java-chassis-dependencies Key: SCB-540 URL: https://issues.apache.org/jira/browse/SCB-540 Project: Apache ServiceComb Issue Type: Sub-task Components: Java-Chassis Affects Versions: java-chassis-1.0.0-m2 Reporter: yangyongzheng Assignee: yangyongzheng Fix For: java-chassis-1.0.0-m2 It's a mistake that is unnecessary for add archetypes into java-chassis-dependencies, we need delete them. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SCB-527) Reorganization All Archetype For Enable Auto Publish
[ https://issues.apache.org/jira/browse/SCB-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng resolved SCB-527. --- Resolution: Fixed > Reorganization All Archetype For Enable Auto Publish > > > Key: SCB-527 > URL: https://issues.apache.org/jira/browse/SCB-527 > Project: Apache ServiceComb > Issue Type: Sub-task > Components: Java-Chassis >Affects Versions: java-chassis-1.0.0-m2 >Reporter: yangyongzheng >Assignee: yangyongzheng >Priority: Major > Fix For: java-chassis-1.0.0-m2 > > > Current archetype is organize for using [`mvn > archetype:create-from-project`](http://maven.apache.org/archetype/maven-archetype-plugin/create-from-project-mojo.html) > to publish,it is not so good for auto build and publish to maven center repo. > We need reorganization all of them using normal [`maven > install`](https://maven.apache.org/guides/mini/guide-creating-archetypes.html) > to generate -archetype.jar and auto publish. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SCB-197) Add a embedded console perfStatics output for debug
[ https://issues.apache.org/jira/browse/SCB-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yangyongzheng closed SCB-197. - Resolution: Fixed > Add a embedded console perfStatics output for debug > --- > > Key: SCB-197 > URL: https://issues.apache.org/jira/browse/SCB-197 > Project: Apache ServiceComb > Issue Type: Wish > Components: Java-Chassis >Reporter: yangyongzheng >Priority: Minor > Labels: beginner, newbie > > we need a embedded console perfStatics replace old PerfStatMonitorMgr in > foundation-metrics: > her is a > example:https://github.com/wujimin/java-chassis/blob/transport-optimize-for-reactive/demo/perf/src/main/java/io/servicecomb/demo/perf/PerfMetricsFilePublisher.java -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCB-88) error occurs when start a service following "quick start"
[
https://issues.apache.org/jira/browse/SCB-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460764#comment-16460764
]
yangyongzheng commented on SCB-88:
--
It seems enabled zipkin tracing but not start up zipkin server (listening on
9411)
> error occurs when start a service following "quick start"
> -
>
> Key: SCB-88
> URL: https://issues.apache.org/jira/browse/SCB-88
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Priority: Major
>
> {code}
> java.net.ConnectException: Failed to connect to /127.0.0.1:9411
> at
> okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:189)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.RealConnection.buildConnection(RealConnection.java:173)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.RealConnection.connect(RealConnection.java:114)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:193)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:129)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:98)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:109)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:124)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:92)
> ~[okhttp-3.4.1.jar:na]
> at
> okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:67)
> ~[okhttp-3.4.1.jar:na]
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:170)
> ~[okhttp-3.4.1.jar:na]
> at okhttp3.RealCall.access$100(RealCall.java:33) ~[okhttp-3.4.1.jar:na]
> at okhttp3.RealCall$AsyncCall.execute(RealCall.java:120)
> ~[okhttp-3.4.1.jar:na]
> at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
> [okhttp-3.4.1.jar:na]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> [na:1.8.0_121]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> [na:1.8.0_121]
> at java.lang.Thread.run(Thread.java:745) [na:1.8.0_121]
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SCB-86) can not find handler :tracing-provider
[
https://issues.apache.org/jira/browse/SCB-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16460489#comment-16460489
]
yangyongzheng commented on SCB-86:
--
In release 1.0.0-m1, `handler-tracing-zipkin` had added in dependencies
```xml
org.springframework.boot
spring-boot-starter
org.apache.servicecomb
spring-boot-starter-provider
org.apache.servicecomb
handler-flowcontrol-qps
org.apache.servicecomb
handler-bizkeeper
org.apache.servicecomb
handler-tracing-zipkin
```
> can not find handler :tracing-provider
> --
>
> Key: SCB-86
> URL: https://issues.apache.org/jira/browse/SCB-86
> Project: Apache ServiceComb
> Issue Type: Bug
> Components: Java-Chassis
>Reporter: Bo Li
>Assignee: yangyongzheng
>Priority: Major
>
> {code}java.lang.Error: can not find handler: tracing-project {code} error
> occurs when runing bmi distributed tracing demo.
> microservice.yaml configuration is:
> {code}
> APPLICATION_ID: bmi
> service_description:
> # name of the declaring microservice
> name: calculator
> version: 0.0.1
> cse:
> service:
> registry:
> address: http://127.0.0.1:30100
> rest:
> address: 0.0.0.0:
> handler:
> chain:
> Provider:
> default: tracing-provider
> {code}
> exception throwed when runing CalculationApplication:
> {code}
> 2017-09-19 11:57:28,586 [ERROR] Application startup failed
> org.springframework.boot.SpringApplication.reportFailure(SpringApplication.java:840)
> java.lang.Error: can not find handler :tracing-provider
> at
> io.servicecomb.core.handler.AbstractHandlerManager.convertToChainClass(AbstractHandlerManager.java:68)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.handler.AbstractHandlerManager.createHandlerChain(AbstractHandlerManager.java:82)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.handler.AbstractHandlerManager.create(AbstractHandlerManager.java:110)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.handler.AbstractHandlerManager.create(AbstractHandlerManager.java:32)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.foundation.common.AbstractObjectManager.getOrCreate(AbstractObjectManager.java:36)
> ~[foundation-common-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.definition.loader.SchemaLoader.registerSchema(SchemaLoader.java:94)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:112)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.definition.schema.ProducerSchemaFactory.createSchema(ProducerSchemaFactory.java:42)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.definition.schema.AbstractSchemaFactory.getOrCreateSchema(AbstractSchemaFactory.java:59)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.definition.schema.ProducerSchemaFactory.getOrCreateProducerSchema(ProducerSchemaFactory.java:75)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.provider.rest.common.RestProducerProvider.init(RestProducerProvider.java:48)
> ~[provider-rest-common-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.provider.producer.ProducerProviderManager.init(ProducerProviderManager.java:43)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> io.servicecomb.core.CseApplicationListener.onApplicationEvent(CseApplicationListener.java:113)
> ~[java-chassis-core-0.3.0-SNAPSHOT.jar:?]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:166)
> ~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:138)
> ~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:383)
> ~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:337)
> ~[spring-context-4.3.4.RELEASE.jar:4.3.4.RELEASE]
> at
> org.springframework.boot.context.event.EventPublishingRunListener.finished(EventPublishingRunListener.java:99)
> ~[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
> at
> org.springframework.boot.SpringApplicationRunListeners.callFinishedListener(SpringApplicationRunListeners.java:79)
> ~[spring-boot-1.4.5.RELEASE.jar:1.4.5.RELEASE]
