Re: [VOTE] Release Apache ServiceComb Pack version 0.4.0 (RC-02)
Hi @bismy @Willem Jiang I follow the steps to try to reproduce your question. 1. I clone the HouseAppWithSpringBoot2 project 2. git reset --hard 2700af4ff0eddc048528d2d06a5a09c904a7f1f8 3. run account-service There are the same problems as you described My solution 1. modify the account-service application.yaml add the following parameters alpha: cluster: address: 0.0.0.0:8080 2. modify common microservice.yaml to modify as follows saga-provider rename to pack-provider saga-consumer rename to pack-consumer account-service started successfully BTW：If you use the consul registry, there is compatibility between the version spring-boot 2.1.x compatibility spring-cloud-starter-consul-discovery 2.1.1 spring-boot 2.0.x compatibility spring-cloud-starter-consul-discovery 2.0.2 Zhang Lei. > 在 2019年4月8日，下午12:54，Willem Jiang 写道： > > oh, you need to put the cse maven repo[1] into your maven setting.xml like > this. > > But I think we can add it into the root pom.xml > > [1]https://github.com/huaweicse/cse-java-chassis-samples/blob/master/HouseAppWithSpringBoot2/settings.xml > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Apr 8, 2019 at 12:07 PM zhang_...@boco.com.cn > wrote: >> >> Hi @bismy @Willem Jiang >> >> I tried to specify the spring boot version to 2.0.4 in my hotel project. The >> following error occurred during startup. This error is due to >> spring-cloud-starter-consul-discovery 2.1.1 and spring boot 2.0.4 >> Incompatible. >> >> . ___ _ _ >> /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ >> ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ >> \\/ ___)| |_)| | | | | || (_| | ) ) ) ) >> ' || .__|_| |_|_| |_\__, | / / / / >> =|_|==|___/=/_/_/_/ >> :: Spring Boot ::(v2.0.4.RELEASE) >> >> 11:49:30.560 [main] INFO org.apache.servicecomb.pack.demo.hotel.Application >> - No active profile set, falling back to default profiles: default >> java.lang.AbstractMethodError >>at >> org.springframework.core.OrderComparator.findOrder(OrderComparator.java:84) >>at >> org.springframework.core.annotation.AnnotationAwareOrderComparator.findOrder(AnnotationAwareOrderComparator.java:65) >>at >> org.springframework.core.OrderComparator.getOrder(OrderComparator.java:72) >>at >> org.springframework.core.OrderComparator.getOrder(OrderComparator.java:67) >>at >> org.springframework.core.OrderComparator.doCompare(OrderComparator.java:38) >>at >> org.springframework.core.OrderComparator.compare(OrderComparator.java:27) >>at java.util.TimSort.countRunAndMakeAscending(TimSort.java:360) >>at java.util.TimSort.sort(TimSort.java:220) >>at java.util.Arrays.sort(Arrays.java:1512) >>at java.util.ArrayList.sort(ArrayList.java:1462) >>at >> org.springframework.boot.SpringApplication.asUnmodifiableOrderedSet(SpringApplication.java:1325) >>at >> org.springframework.boot.SpringApplication.getListeners(SpringApplication.java:1234) >>at >> org.springframework.boot.context.event.EventPublishingRunListener.contextLoaded(EventPublishingRunListener.java:85) >>at >> org.springframework.boot.SpringApplicationRunListeners.contextLoaded(SpringApplicationRunListeners.java:66) >>at >> org.springframework.boot.SpringApplication.prepareContext(SpringApplication.java:394) >>at >> org.springframework.boot.SpringApplication.run(SpringApplication.java:328) >>at >> org.springframework.boot.SpringApplication.run(SpringApplication.java:1258) >>at >> org.springframework.boot.SpringApplication.run(SpringApplication.java:1246) >>at >> org.apache.servicecomb.pack.demo.hotel.Application.main(Application.java:28) >> >> >> But I didn't reproduce LiuBao's error. Please tell me the spring boot >> version used by project HouseAppWithSpringBoot2, I tried to compile >> HouseAppWithSpringBoot2 but the prompt is as follows >> >> [ERROR] [ERROR] Some problems were encountered while processing the POMs: >> [ERROR] Non-resolvable import POM: Failure to find >> com.huawei.paas.cse:cse-dependency-spring-boot2:pom:2.3.62 in >> https://repo.maven.apache.org/maven2 was cached in the local repository, >> resolution will not be reattempted until the update interval of central has >> elapsed or updates are forced @ line 34, column 19 >> >> >> Thanks, >> Zhang Lei. >> >> >> >>> 在 2019年4月5日，下午4:51，bismy 写道： >>> >>> I tried following command and resolved the problem: >>>
Re: [VOTE] Release Apache ServiceComb Pack version 0.4.0 (RC-02)
org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:474)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1247)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1096)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:535)
> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:495)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:317)
> at
> org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:315)
> at
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:204)
> at
> org.springframework.context.support.PostProcessorRegistrationDelegate.registerBeanPostProcessors(PostProcessorRegistrationDelegate.java:236)
> at
> org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:710)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:535)
> at
> org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:140)
> at
> org.springframework.boot.SpringApplication.refresh(SpringApplication.java:762)
> at
> org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:398)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:330)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1258)
> at
> org.springframework.boot.SpringApplication.run(SpringApplication.java:1246)
> at
> com.huawei.cse.houseapp.account.AccountApplication.main(AccountApplication.java:12)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48)
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:87)
> at org.springframework.boot.loader.Launcher.launch(Launcher.java:50)
> at
> org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:51)
> Caused by: org.springframework.beans.factory.NoSuchBeanDefinitionException:
> No qualifying bean of type
> 'org.apache.servicecomb.pack.omega.context.OmegaContext' available: expected
> at least 1 bean which qualifies as autowire candidate. Dependency
> annotations: {}
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.raiseNoMatchingBeanFound(DefaultListableBeanFactory.java:1506)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.doResolveDependency(DefaultListableBeanFactory.java:1101)
> at
> org.springframework.beans.factory.support.DefaultListableBeanFactory.resolveDependency(DefaultListableBeanFactory.java:1062)
> at
> org.springframework.beans.factory.support.ConstructorResolver.resolveAutowiredArgument(ConstructorResolver.java:818)
> at
> org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:724)
>
>
> -- 原始邮件 --
> 发件人: "zhang_...@boco.com.cn";
> 发送时间: 2019年4月4日(星期四) 下午3:42
> 收件人: "dev";
> 主题: Re: [VOTE] Release Apache ServiceComb Pack version 0.4.0 (RC-02)
>
> You can try this startup script
>
> java -Dloader.path=./libs \
> -jar alpha-server-0.4.0-SNAPSHOT-exec.jar \
> --spring.profiles.active=mysql \
> --spring.datasource.url="jdbc:mysql://127.0.0.1:3306/saga?serverTimezone=GMT%2b8=false"
> \
> --spring.datasource.username=saga-user \
> --spring.datasource.password=saga-password
>
>
> > 在 2019年4月4日，下午3:20，bismy 写道：
> >
> > I am trying to run sage demos, but I got this error when start alpha. Any
> > ideas?
> >
> >
> > My steps:
> > 1. Download binary release, and copy mysql-connector-java-8.0.12.jar to
> > libs folder.
Re: [VOTE] Release Apache ServiceComb Pack version 0.4.0 (RC-02)
Hi @bi...@qq.com, @Willem Jiang
Avoid confusion with the same name directory in the distribution package, I
submitted a PR https://github.com/apache/servicecomb-pack/pull/448, modify the
directory name libs to plugins in the documentation
> 在 2019年4月4日，下午3:20，bismy 写道：
>
> I am trying to run sage demos, but I got this error when start alpha. Any
> ideas?
>
>
> My steps:
> 1. Download binary release, and copy mysql-connector-java-8.0.12.jar to libs
> folder. And mysql is stared.
> 2. running
>java -Dspring.profiles.active=mysql -Dloader.path=./libs
> -D"spring.datasource.url=jdbc:mysql://localhost:3306/saga?useSSL=false"
> -Dspring.datasource.username= -Dspring.datasource.password= -jar
> alpha-server-0.4.0-exec.jar
>
>
> start up error message
> 15:12:59.323 [main] INFO
> org.apache.servicecomb.pack.alpha.server.AlphaApplication - The following
> profiles are active: mysql
> 2019-04-04 15:13:00.678 INFO 8328 --- [ main]
> .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data
> repositories in DEFAULT mode.
> 2019-04-04 15:13:00.867 INFO 8328 --- [ main]
> .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository
> scanning in 168ms. Found 7 repository interfaces.
> 15:13:01.763 [main] INFO
> org.springframework.cloud.context.scope.GenericScope - BeanFactory
> id=aca50879-d81b-337a-9511-e75e77dd8564
> 15:13:01.975 [main] INFO
> org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker
> - Bean
> 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration'
> of type
> [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$fd4cf6c]
> is not eligible for getting processed by all BeanPostProcessors (for
> example: not eligible for auto-proxying)
> 15:13:02.247 [main] INFO
> org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker
> - Bean
> 'org.apache.servicecomb.pack.omega.transaction.spring.TransactionAspectConfig'
> of type
> [org.apache.servicecomb.pack.omega.transaction.spring.TransactionAspectConfig$$EnhancerBySpringCGLIB$$782e0f4c]
> is not eligible for getting processed by all BeanPostProcessors (for
> example: not eligible for auto-proxying)
> 15:13:02.273 [main] WARN
> org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext
> - Exception encountered during context initialization - cancelling refresh
> attempt: org.springframework.beans.factory.UnsatisfiedDependencyException:
> Error creating bean with name 'compensableAnnotationProcessor' defined in
> class path resource
> [org/apache/servicecomb/pack/omega/transaction/spring/TransactionAspectConfig.class]:
> Unsatisfied dependency expressed through method
> 'compensableAnnotationProcessor' parameter 0; nested exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> qualifying bean of type
> 'org.apache.servicecomb.pack.omega.context.OmegaContext' available: expected
> at least 1 bean which qualifies as autowire candidate. Dependency
> annotations: {}
> 15:13:02.291 [main] INFO
> org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLoggingListener
> -
>
>
> Error starting ApplicationContext. To display the conditions report re-run
> your application with 'debug' enabled.
> 15:13:02.698 [main] ERROR
> org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter -
>
>
> ***
> APPLICATION FAILED TO START
> ***
>
>
> Description:
>
>
> Parameter 0 of method compensableAnnotationProcessor in
> org.apache.servicecomb.pack.omega.transaction.spring.TransactionAspectConfig
> required a bean of type
> 'org.apache.servicecomb.pack.omega.context.OmegaContext' that could not be
> found.
>
>
> The following candidates were found but could not be injected:
>- Bean method 'omegaContext' in 'OmegaSpringConfig' not loaded because
> @ConditionalOnProperty (alpha.cluster.address) did not find property
> 'alpha.cluster.address'
>
>
>
>
> Action:
>
>
> Consider revisiting the entries above or defining a bean of type
> 'org.apache.servicecomb.pack.omega.context.OmegaContext' in your
> configuration.
>
>
> 15:13:02.698 [main] ERROR
> org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter -
>
>
> ***
> APPLICATION FAILED TO START
> ***
>
>
> Description:
>
>
> Parameter 0 of method compensableAnnotationProcessor in
> org.apache.servicecomb.pack.omega.transaction.spring.TransactionAspectConfig
> required a bean of type
> 'org.apache.servicecomb.pack.omega.context.OmegaContext' that could not be
> found.
>
>
> The following candidates were found but could not be injected:
>- Bean method 'omegaContext' in
Re: [VOTE] Release Apache ServiceComb Pack version 0.4.0 (RC-02)
Oh, I guessed it.
Do not use the libs directory in the
apache-servicecomb-pack-distribution-0.4.0-bin, because it contains all the
jars.
You can create a new libs2 directory and copy mysql-connector-java-8.0.12.jar
to libs2 folder
> 在 2019年4月4日，下午3:20，bismy 写道：
>
> I am trying to run sage demos, but I got this error when start alpha. Any
> ideas?
>
>
> My steps:
> 1. Download binary release, and copy mysql-connector-java-8.0.12.jar to libs
> folder. And mysql is stared.
> 2. running
>java -Dspring.profiles.active=mysql -Dloader.path=./libs
> -D"spring.datasource.url=jdbc:mysql://localhost:3306/saga?useSSL=false"
> -Dspring.datasource.username= -Dspring.datasource.password= -jar
> alpha-server-0.4.0-exec.jar
>
>
> start up error message
> 15:12:59.323 [main] INFO
> org.apache.servicecomb.pack.alpha.server.AlphaApplication - The following
> profiles are active: mysql
> 2019-04-04 15:13:00.678 INFO 8328 --- [ main]
> .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data
> repositories in DEFAULT mode.
> 2019-04-04 15:13:00.867 INFO 8328 --- [ main]
> .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository
> scanning in 168ms. Found 7 repository interfaces.
> 15:13:01.763 [main] INFO
> org.springframework.cloud.context.scope.GenericScope - BeanFactory
> id=aca50879-d81b-337a-9511-e75e77dd8564
> 15:13:01.975 [main] INFO
> org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker
> - Bean
> 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration'
> of type
> [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$fd4cf6c]
> is not eligible for getting processed by all BeanPostProcessors (for
> example: not eligible for auto-proxying)
> 15:13:02.247 [main] INFO
> org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker
> - Bean
> 'org.apache.servicecomb.pack.omega.transaction.spring.TransactionAspectConfig'
> of type
> [org.apache.servicecomb.pack.omega.transaction.spring.TransactionAspectConfig$$EnhancerBySpringCGLIB$$782e0f4c]
> is not eligible for getting processed by all BeanPostProcessors (for
> example: not eligible for auto-proxying)
> 15:13:02.273 [main] WARN
> org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext
> - Exception encountered during context initialization - cancelling refresh
> attempt: org.springframework.beans.factory.UnsatisfiedDependencyException:
> Error creating bean with name 'compensableAnnotationProcessor' defined in
> class path resource
> [org/apache/servicecomb/pack/omega/transaction/spring/TransactionAspectConfig.class]:
> Unsatisfied dependency expressed through method
> 'compensableAnnotationProcessor' parameter 0; nested exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> qualifying bean of type
> 'org.apache.servicecomb.pack.omega.context.OmegaContext' available: expected
> at least 1 bean which qualifies as autowire candidate. Dependency
> annotations: {}
> 15:13:02.291 [main] INFO
> org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLoggingListener
> -
>
>
> Error starting ApplicationContext. To display the conditions report re-run
> your application with 'debug' enabled.
> 15:13:02.698 [main] ERROR
> org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter -
>
>
> ***
> APPLICATION FAILED TO START
> ***
>
>
> Description:
>
>
> Parameter 0 of method compensableAnnotationProcessor in
> org.apache.servicecomb.pack.omega.transaction.spring.TransactionAspectConfig
> required a bean of type
> 'org.apache.servicecomb.pack.omega.context.OmegaContext' that could not be
> found.
>
>
> The following candidates were found but could not be injected:
>- Bean method 'omegaContext' in 'OmegaSpringConfig' not loaded because
> @ConditionalOnProperty (alpha.cluster.address) did not find property
> 'alpha.cluster.address'
>
>
>
>
> Action:
>
>
> Consider revisiting the entries above or defining a bean of type
> 'org.apache.servicecomb.pack.omega.context.OmegaContext' in your
> configuration.
>
>
> 15:13:02.698 [main] ERROR
> org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter -
>
>
> ***
> APPLICATION FAILED TO START
> ***
>
>
> Description:
>
>
> Parameter 0 of method compensableAnnotationProcessor in
> org.apache.servicecomb.pack.omega.transaction.spring.TransactionAspectConfig
> required a bean of type
> 'org.apache.servicecomb.pack.omega.context.OmegaContext' that could not be
> found.
>
>
> The following candidates were found but could not be injected:
>- Bean method 'omegaContext' in 'OmegaSpringConfig' not
Re: [VOTE] Release Apache ServiceComb Pack version 0.4.0 (RC-02)
Please send your full log file to 760...@qq.com Zhang Lei. > 在 2019年4月4日，下午3:20，bismy 写道： > > OmegaSpringConfig
Re: [VOTE] Release Apache ServiceComb Pack version 0.4.0 (RC-02)
You can try this startup script
java -Dloader.path=./libs \
-jar alpha-server-0.4.0-SNAPSHOT-exec.jar \
--spring.profiles.active=mysql \
--spring.datasource.url="jdbc:mysql://127.0.0.1:3306/saga?serverTimezone=GMT%2b8=false"
\
--spring.datasource.username=saga-user \
--spring.datasource.password=saga-password
> 在 2019年4月4日，下午3:20，bismy 写道：
>
> I am trying to run sage demos, but I got this error when start alpha. Any
> ideas?
>
>
> My steps:
> 1. Download binary release, and copy mysql-connector-java-8.0.12.jar to libs
> folder. And mysql is stared.
> 2. running
>java -Dspring.profiles.active=mysql -Dloader.path=./libs
> -D"spring.datasource.url=jdbc:mysql://localhost:3306/saga?useSSL=false"
> -Dspring.datasource.username= -Dspring.datasource.password= -jar
> alpha-server-0.4.0-exec.jar
>
>
> start up error message
> 15:12:59.323 [main] INFO
> org.apache.servicecomb.pack.alpha.server.AlphaApplication - The following
> profiles are active: mysql
> 2019-04-04 15:13:00.678 INFO 8328 --- [ main]
> .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data
> repositories in DEFAULT mode.
> 2019-04-04 15:13:00.867 INFO 8328 --- [ main]
> .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository
> scanning in 168ms. Found 7 repository interfaces.
> 15:13:01.763 [main] INFO
> org.springframework.cloud.context.scope.GenericScope - BeanFactory
> id=aca50879-d81b-337a-9511-e75e77dd8564
> 15:13:01.975 [main] INFO
> org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker
> - Bean
> 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration'
> of type
> [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$fd4cf6c]
> is not eligible for getting processed by all BeanPostProcessors (for
> example: not eligible for auto-proxying)
> 15:13:02.247 [main] INFO
> org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker
> - Bean
> 'org.apache.servicecomb.pack.omega.transaction.spring.TransactionAspectConfig'
> of type
> [org.apache.servicecomb.pack.omega.transaction.spring.TransactionAspectConfig$$EnhancerBySpringCGLIB$$782e0f4c]
> is not eligible for getting processed by all BeanPostProcessors (for
> example: not eligible for auto-proxying)
> 15:13:02.273 [main] WARN
> org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext
> - Exception encountered during context initialization - cancelling refresh
> attempt: org.springframework.beans.factory.UnsatisfiedDependencyException:
> Error creating bean with name 'compensableAnnotationProcessor' defined in
> class path resource
> [org/apache/servicecomb/pack/omega/transaction/spring/TransactionAspectConfig.class]:
> Unsatisfied dependency expressed through method
> 'compensableAnnotationProcessor' parameter 0; nested exception is
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No
> qualifying bean of type
> 'org.apache.servicecomb.pack.omega.context.OmegaContext' available: expected
> at least 1 bean which qualifies as autowire candidate. Dependency
> annotations: {}
> 15:13:02.291 [main] INFO
> org.springframework.boot.autoconfigure.logging.ConditionEvaluationReportLoggingListener
> -
>
>
> Error starting ApplicationContext. To display the conditions report re-run
> your application with 'debug' enabled.
> 15:13:02.698 [main] ERROR
> org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter -
>
>
> ***
> APPLICATION FAILED TO START
> ***
>
>
> Description:
>
>
> Parameter 0 of method compensableAnnotationProcessor in
> org.apache.servicecomb.pack.omega.transaction.spring.TransactionAspectConfig
> required a bean of type
> 'org.apache.servicecomb.pack.omega.context.OmegaContext' that could not be
> found.
>
>
> The following candidates were found but could not be injected:
>- Bean method 'omegaContext' in 'OmegaSpringConfig' not loaded because
> @ConditionalOnProperty (alpha.cluster.address) did not find property
> 'alpha.cluster.address'
>
>
>
>
> Action:
>
>
> Consider revisiting the entries above or defining a bean of type
> 'org.apache.servicecomb.pack.omega.context.OmegaContext' in your
> configuration.
>
>
> 15:13:02.698 [main] ERROR
> org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter -
>
>
> ***
> APPLICATION FAILED TO START
> ***
>
>
> Description:
>
>
> Parameter 0 of method compensableAnnotationProcessor in
> org.apache.servicecomb.pack.omega.transaction.spring.TransactionAspectConfig
> required a bean of type
> 'org.apache.servicecomb.pack.omega.context.OmegaContext' that could not be
> found.
>
>
> The following candidates were found but could not
Re: [DISCUSS] Require the review before merging the PR
+1 > 在 2019年4月3日，下午2:55，Zheng Feng 写道： > > Hi, > > I just wonder if we can enable this setting [1] on servicecomb-pack [2] and > it could be helpful when reviewing the PR. I think at least one people > review the changes and approve before merging it. We have to raise a JIRA > for the infra team to do this setting. So I post this message here to see > if the others have any thought. > > Regards, > Zheng Feng > > [1] > https://help.github.com/en/articles/enabling-required-reviews-for-pull-requests > [2] https://github.com/apache/servicecomb-pack Zhang Lei.
Re: [ANN] New ServiceComb committer: Zhang Lei (张磊）
I am very happy to learn to grow together with everyone. Thanks, Zhang Lei. > 在 2019年4月1日，下午11:19，Willem Jiang 写道： > > Sorry, there is a typo in the first mail. The first sentence should be: > > Please join me and the rest of the ServiceComb PPMC members in welcoming our > new ServiceComb committer: Zhang Lei (张磊). > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Apr 1, 2019 at 10:53 PM Willem Jiang wrote: >> >> Please join me and the rest of the ServiceComb PPMC members in welcoming our >> new ServiceComb committer: Zhang Lei (赵俊). >> >> Zhang Lei contribute the ServiceComb earlier this year， he is active >> contributor on pack project and the mailing list, and we look >> forward to many more contributions in the future. >> >> Congratulations to Zhang Lei! Welcome! >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem
Re: [ANN] New ServiceComb committer: Zhang Lei (张磊）
I went to confirm the official mail again. (*^__^*) Zhang Lei. > 在 2019年4月1日，下午11:30，Zheng Feng 写道： > > I just think it was the April fools Day message :) > > Willem Jiang 于2019年4月1日周一 下午11:19写道： > >> Sorry, there is a typo in the first mail. The first sentence should be: >> >> Please join me and the rest of the ServiceComb PPMC members in welcoming >> our >> new ServiceComb committer: Zhang Lei (张磊). >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> On Mon, Apr 1, 2019 at 10:53 PM Willem Jiang >> wrote: >>> >>> Please join me and the rest of the ServiceComb PPMC members in welcoming >> our >>> new ServiceComb committer: Zhang Lei (赵俊). >>> >>> Zhang Lei contribute the ServiceComb earlier this year， he is active >>> contributor on pack project and the mailing list, and we look >>> forward to many more contributions in the future. >>> >>> Congratulations to Zhang Lei! Welcome! >>> >>> Willem Jiang >>> >>> Twitter: willemjiang >>> Weibo: 姜宁willem >>
Re: [ANN] New ServiceComb committer: Zhang Lei (张磊）
I went to confirm the official mail again. (*^__^*) Zhang Lei. > 在 2019年4月1日，下午11:30，Zheng Feng 写道： > > I just think it was the April fools Day message :) > > Willem Jiang 于2019年4月1日周一 下午11:19写道： > >> Sorry, there is a typo in the first mail. The first sentence should be: >> >> Please join me and the rest of the ServiceComb PPMC members in welcoming >> our >> new ServiceComb committer: Zhang Lei (张磊). >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> On Mon, Apr 1, 2019 at 10:53 PM Willem Jiang >> wrote: >>> >>> Please join me and the rest of the ServiceComb PPMC members in welcoming >> our >>> new ServiceComb committer: Zhang Lei (赵俊). >>> >>> Zhang Lei contribute the ServiceComb earlier this year， he is active >>> contributor on pack project and the mailing list, and we look >>> forward to many more contributions in the future. >>> >>> Congratulations to Zhang Lei! Welcome! >>> >>> Willem Jiang >>> >>> Twitter: willemjiang >>> Weibo: 姜宁willem >>
Re: [VOTE] Release Apache ServiceComb Pack version 0.4.0
I agree, this will avoid mistakes Zhang Lei. > 在 2019年4月1日，下午3:26，Zheng Feng 写道： > > So do we have to do the license checking by using the license-maven-plugin ? > > Willem Jiang 于2019年4月1日周一 下午3:10写道： > >> I checked the staging repo by running the demo against it. >> But I found Alpha introduced a (LGPL 3.0 license) Compact HashMap >> (com.github.vlsi.compactmap:compactmap:1.2.1 - >> https://github.com/vlsi/compactmap/compactmap) , we need to exclude it >> from our apache release. >> >> So I have to vote -1 for it. >> Now I'm working on the generate the third party license file to avoid >> this kind of error in the future. >> >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> On Sat, Mar 30, 2019 at 9:25 AM Mohammad Asif Siddiqui >> wrote: >>> >>> Hi All, >>> >>> This is a call for Vote to release Apache ServiceComb Pack version 0.4.0 >>> >>> Release Candidate : >> https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-pack/0.4.0/rc-01/ >>> >>> Staging Repository : >> https://repository.apache.org/content/repositories/orgapacheservicecomb-1379 >>> >>> Release Tag : >> https://github.com/apache/servicecomb-pack/releases/tag/0.4.0 >>> >>> Release CommitID : 32588a3253d5e4573ade849c37eedd371580b1fd >>> >>> Release Notes : >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12344102 >>> >>> Keys to verify the Release Candidate : >> https://dist.apache.org/repos/dist/dev/servicecomb/KEYS >>> >>> Voting will start now ( Saturday, 30th March, 2019) and will remain open >> for at-least 72 hours, Request all PMC members to give their vote. >>> >>> [ ] +1 Release this package as 0.4.0 >>> [ ] +0 No Opinion >>> [ ] -1 Do not release this package because >>> >>> On the behalf of ServiceComb Team >>> Mohammad Asif Siddiqui >>
Re: [VOTE] Release Apache ServiceComb Pack version 0.4.0
eureka-client.jar dependent a (LGPL 3.0 license) Compact HashMap (com.github.vlsi.compactmap:compactmap:1.2.1 - https://github.com/vlsi/compactmap/compactmap) I have removed the dependency on eureka from the release version on this PR https://github.com/apache/servicecomb-pack/pull/444 . We can build support eureka version with '-Pspring-cloud-eureka' parameter Zhang Lei. > 在 2019年4月1日，下午3:10，Willem Jiang 写道： > > I checked the staging repo by running the demo against it. > But I found Alpha introduced a (LGPL 3.0 license) Compact HashMap > (com.github.vlsi.compactmap:compactmap:1.2.1 - > https://github.com/vlsi/compactmap/compactmap) , we need to exclude it > from our apache release. > > So I have to vote -1 for it. > Now I'm working on the generate the third party license file to avoid > this kind of error in the future. > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Sat, Mar 30, 2019 at 9:25 AM Mohammad Asif Siddiqui > wrote: >> >> Hi All, >> >> This is a call for Vote to release Apache ServiceComb Pack version 0.4.0 >> >> Release Candidate : >> https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-pack/0.4.0/rc-01/ >> >> Staging Repository : >> https://repository.apache.org/content/repositories/orgapacheservicecomb-1379 >> >> Release Tag : https://github.com/apache/servicecomb-pack/releases/tag/0.4.0 >> >> Release CommitID : 32588a3253d5e4573ade849c37eedd371580b1fd >> >> Release Notes : >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626=12344102 >> >> Keys to verify the Release Candidate : >> https://dist.apache.org/repos/dist/dev/servicecomb/KEYS >> >> Voting will start now ( Saturday, 30th March, 2019) and will remain open for >> at-least 72 hours, Request all PMC members to give their vote. >> >> [ ] +1 Release this package as 0.4.0 >> [ ] +0 No Opinion >> [ ] -1 Do not release this package because >> >> On the behalf of ServiceComb Team >> Mohammad Asif Siddiqui
Re: Microsoft Orleans Brings Distributed Transactions to Cloud
Do we need to do some pre-research work on akka? E.g. 1. fsm 2. persistence 3. cluster Zhang Lei. > 在 2019年3月19日，上午11:40，Willem Jiang 写道： > > Yeah, it's an exciting news. > I just found another paper[1] of Phil after went through the news. > > Using Akka to rewrite the Alpha server is in my mind for a while. Let > us go through the papers and find out if there any new work we could > do in the future version of ServiceComb Pack. > > [1]https://www.microsoft.com/en-us/research/wp-content/uploads/2016/10/EldeebBernstein-TransactionalActors-MSR-TR-1.pdf > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Tue, Mar 19, 2019 at 8:46 AM Zheng Feng wrote: >> >> https://thenewstack.io/microsoft-orleans-brings-distributed-transactions-to-cloud/ >> It could be interesting and they used Phil's paper [1]. >> >> Regards, >> Zheng Feng >> >> [1] >> https://www.amazon.com/Concurrency-Control-Recovery-Database-Systems/dp/0201107155
Re: Release of ServiceComb
verification all passed with spring-boot-1 and spring-boot-2 # Cluster 1. alpha cluster master node switch - Pass 2. random gRPC port - Pass 3. alpha cluster with random gRPC port - Pass # Eureka 4. alpha register to Eureka - Pass 5. alpha cluster register to Eureka - Pass 6. alpha cluster register to Eureka with random gRPC port - Pass # Consul 7. alpha register to Consul - Pass 8. alpha cluster register to Consul - Pass 9. alpha cluster register to Consul with random gRPC port - Pass # Test instruction 1. alpha cluster master node switch java -jar alpha-server-0.4.0-SNAPSHOT-exec.jar \ --spring.profiles.active=prd \ --server.port=0 \ --alpha.server.port=8080 \ --spring.datasource.url="jdbc:postgresql://localhost:5432/saga?useSSL=false" \ --spring.datasource.username=saga-user \ --spring.datasource.password=saga-password \ --alpha.cluster.master.enabled=true java -jar alpha-server-0.4.0-SNAPSHOT-exec.jar \ --spring.profiles.active=prd \ --server.port=0 \ --alpha.server.port=8081 \ --spring.datasource.url="jdbc:postgresql://localhost:5432/saga?useSSL=false" \ --spring.datasource.username=saga-user \ --spring.datasource.password=saga-password \ --alpha.cluster.master.enabled=true java -jar alpha-server-0.4.0-SNAPSHOT-exec.jar \ --spring.profiles.active=prd \ --server.port=0 \ --alpha.server.port=8082 \ --spring.datasource.url="jdbc:postgresql://localhost:5432/saga?useSSL=false" \ --spring.datasource.username=saga-user \ --spring.datasource.password=saga-password \ --alpha.cluster.master.enabled=true 2. random gRPC port java -jar alpha-server-0.4.0-SNAPSHOT-exec.jar \ --spring.profiles.active=prd \ --server.port=0 \ --alpha.server.port=0 \ --spring.datasource.url="jdbc:postgresql://localhost:5432/saga?useSSL=false" \ --spring.datasource.username=saga-user \ --spring.datasource.password=saga-password 3. alpha cluster with random gRPC port repeat three times java -jar alpha-server-0.4.0-SNAPSHOT-exec.jar \ --spring.profiles.active=prd \ --server.port=0 \ --alpha.server.port=0 \ --spring.datasource.url="jdbc:postgresql://localhost:5432/saga?useSSL=false" \ --spring.datasource.username=saga-user \ --spring.datasource.password=saga-password 4. alpha register to Eureka java -jar alpha-server-0.4.0-SNAPSHOT-exec.jar \ --spring.profiles.active=prd \ --spring.datasource.url="jdbc:postgresql://localhost:5432/saga?useSSL=false" \ --spring.datasource.username=saga-user \ --spring.datasource.password=saga-password \ --eureka.client.enabled=true \ --eureka.client.service-url.defaultZone=http://127.0.0.1:8761/eureka 5. alpha cluster register to Eureka java -jar alpha-server-0.4.0-SNAPSHOT-exec.jar \ --spring.profiles.active=prd \ --server.port=0 \ --alpha.server.port=8080 \ --spring.datasource.url="jdbc:postgresql://localhost:5432/saga?useSSL=false" \ --spring.datasource.username=saga-user \ --spring.datasource.password=saga-password \ --alpha.cluster.master.enabled=true \ --eureka.client.enabled=true \ --eureka.client.service-url.defaultZone=http://127.0.0.1:8761/eureka java -jar alpha-server-0.4.0-SNAPSHOT-exec.jar \ --spring.profiles.active=prd \ --server.port=0 \ --alpha.server.port=8081 \ --spring.datasource.url="jdbc:postgresql://localhost:5432/saga?useSSL=false" \ --spring.datasource.username=saga-user \ --spring.datasource.password=saga-password \ --alpha.cluster.master.enabled=true \ --eureka.client.enabled=true \ --eureka.client.service-url.defaultZone=http://127.0.0.1:8761/eureka java -jar alpha-server-0.4.0-SNAPSHOT-exec.jar \ --spring.profiles.active=prd \ --server.port=0 \ --alpha.server.port=8082 \ --spring.datasource.url="jdbc:postgresql://localhost:5432/saga?useSSL=false" \ --spring.datasource.username=saga-user \ --spring.datasource.password=saga-password \ --alpha.cluster.master.enabled=true \ --eureka.client.enabled=true \ --eureka.client.service-url.defaultZone=http://127.0.0.1:8761/eureka 6. alpha cluster register to Eureka with random gRPC port repeat three times java -jar alpha-server-0.4.0-SNAPSHOT-exec.jar \ --spring.profiles.active=prd \ --server.port=0 \ --alpha.server.port=0 \ --spring.datasource.url="jdbc:postgresql://localhost:5432/saga?useSSL=false" \ --spring.datasource.username=saga-user \ --spring.datasource.password=saga-password \ --alpha.cluster.master.enabled=true \
Re: Release of ServiceComb
OK. I will pull master branch and test again. coolbeevip BOCO > 在 2019年3月26日，上午8:59，Willem Jiang 写道： > > Hi Zhanglei, > > Thanks for the verification. I just merged the PRs into master branch. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > On Mon, Mar 25, 2019 at 7:14 PM wrote: >> >> I used the release version locally to complete the following tests >> >> # Cluster >> 1. alpha cluster master node switch - Pass >> 2. random gRPC port - Pass >> 3. alpha cluster with random gRPC port - Failure >> >> # Eureka >> 4. alpha register to Eureka - Pass >> 5. alpha cluster register to Eureka - Pass >> 6. alpha cluster register to Eureka with random gRPC port - Pass >> >> # Consul >> 7. alpha register to Consul - Pass >> 8. alpha cluster register to Consul - Pass >> 9. alpha cluster register to Consul with random gRPC port - Failure >> >> The two failed tests are related to random ports, I have submitted PR to >> solve >> 3. alpha cluster with random gRPC port - Fixed SCB-1216 >> 9. alpha cluster register to Consul with random gRPC port - Fixed SCB-1217 >> >> >> coolbeevip >> >> BOCO >> >> >> >>> 在 2019年3月6日，下午2:29，Willem Jiang 写道： >>> >>> It's time for us to think about ServiceComb release now. >>> >>> As usual, we will release ServiceComb Java-Chassis 1.2.0, ServiceComb >>> ServiceCenter 1.2.0 at the end of this month, then we will release >>> ServiceComb Pack 0.4.0. >>> >>> Please reply the mail if you have any questions about the release plan. >>> >>> Willem Jiang >>> >>> Twitter: willemjiang >>> Weibo: 姜宁willem >>
Re: [Saga] Ask questions about the Saga transaction process
Thank you for your reply, I think about it again. coolbeevip BOCO > 在 2019年3月22日，上午10:52，Willem Jiang 写道： > > For the timeout part, it's the hardest part of ServiceComb Pack. > Current we just deal it in a simple way： > Once the ServiceInvoker (Hotel) found out there is a timeout event, > it just send AbortEvent to the Alpha and end the whole transaction. > > For the TxEnded after the TxAbortEvent issue, we can address it by > letting Omega throw the exception when it received the response from > Alpha (Alpha should know the transaction is aborted at that time) > In this way, we could leverage the @Tranactional feature that Spring > provides to revert the local transaction without sending out the > compensation command. > > Any thought about that? > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Thu, Mar 21, 2019 at 11:47 AM zhang_...@boco.com.cn > wrote: >> >> The following link is a sequence diagram, step 4 cannot be compensated. Will >> this happen? >> >> https://github.com/coolbeevip/servicecomb-pack-notes/blob/master/ServiceComb%20Alpha%20EventScanner/assets/sequence-booking-request-hotel-timeout.png?raw=true >> >> coolbeevip >> >> BOCO >> >> >>
Re: [Saga] Ask questions about the Saga transaction process
This is a light version https://raw.githubusercontent.com/coolbeevip/servicecomb-pack-notes/master/ServiceComb%20Alpha%20Saga/assets/sequence-booking-request-hotel-timeout.png 张 磊 部门: 亿阳信通IT运维支撑产品线 地址: 北京市海淀区杏石口路99号西山赢府商务中心2410 邮编: 100093 手机: 18610099300 移邮：zhang_...@boco.com.cn > 在 2019年3月21日，上午11:47，zhang_...@boco.com.cn 写道： > > The following link is a sequence diagram, step 4 cannot be compensated. Will > this happen? > > https://github.com/coolbeevip/servicecomb-pack-notes/blob/master/ServiceComb%20Alpha%20EventScanner/assets/sequence-booking-request-hotel-timeout.png?raw=true > > coolbeevip > > BOCO > > >
[Saga] Ask questions about the Saga transaction process
The following link is a sequence diagram, step 4 cannot be compensated. Will this happen? https://github.com/coolbeevip/servicecomb-pack-notes/blob/master/ServiceComb%20Alpha%20EventScanner/assets/sequence-booking-request-hotel-timeout.png?raw=true coolbeevip BOCO
Re: Release of ServiceComb
I will update the document about alpha support consul later today coolbeevip BOCO > 在 2019年3月19日，下午4:54，Willem Jiang 写道： > > As we talked, it's time to prepare the release. > There is only ten days to the end of this month, we need to make sure > the branches are ready to go. > Please reply this mail if you have any other big patch need to go with > this release, otherwise we will start the release process shortly. > > @Asif Do you mind start the release check? > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Wed, Mar 6, 2019 at 2:29 PM Willem Jiang wrote: >> >> It's time for us to think about ServiceComb release now. >> >> As usual, we will release ServiceComb Java-Chassis 1.2.0, ServiceComb >> ServiceCenter 1.2.0 at the end of this month, then we will release >> ServiceComb Pack 0.4.0. >> >> Please reply the mail if you have any questions about the release plan. >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem
Re: Release of ServiceComb
+1 Please merge my PR https://github.com/apache/servicecomb-pack/pull/420 before this coolbeevip BOCO > 在 2019年3月6日，下午2:29，Willem Jiang 写道： > > It's time for us to think about ServiceComb release now. > > As usual, we will release ServiceComb Java-Chassis 1.2.0, ServiceComb > ServiceCenter 1.2.0 at the end of this month, then we will release > ServiceComb Pack 0.4.0. > > Please reply the mail if you have any questions about the release plan. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem
Re: [discuss][java-chassis] new feature for inspect internal status of a microservice instance
Maybe you can customize it with spring boot actuator & metrics coolbeevip BOCO > 在 2019年3月5日，上午9:20，wjm wjm 写道： > > currently it's difficult to collect internal status of a microservice > instance when some problem happened. > eg: > routing depend on cached instances, discovery tree, strategy of > governances, and so on > when we resolving routing related problem, we can only guess the status of > all related modules. > > so we should provide a way to inspect the internal status of a microservice > instance at runtime, maybe include: > • discovery tree > • isolation > • eventbus > • view schemas as swagger or html/pdf.. > • .. > maybe like the gif: > > > my question: > • provide these informations include related html/js/css by instance > directly, or only by governance console > if provide by both instance and governance console, that will cause duplicate > development > • if provide by instance > • what's the name of the module? "inspector"? > • swagger to html depend on "asciidoctor", which depend on > jruby, it's very heavy. > • in my demo, resource of swagger and asciidoctor all load from > cdn, but for some customer's environment, maybe can not connect to internet. > • any other idea?
Re: [discuss][pack]About Alpha module naming
OK, Thanks for your reminder coolbeevip BOCO > 在 2019年2月28日，下午2:27，Willem Jiang 写道： > > We could set the spring-cloud-eureka profile to be activated by > default, if the user want to switch to other service discovery > module, we could change it. > BTW, we need to update the License file[1] for the new third party > dependencies we introduced. > > [1]https://github.com/apache/servicecomb-pack/blob/master/distribution/src/release/LICENSE > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Thu, Feb 28, 2019 at 12:03 PM zhang_...@boco.com.cn > wrote: >> >> Solution about https://issues.apache.org/jira/browse/SCB-1180 >> >> We can include spring-cloud-starter-netflix-eureka-client dependencies by >> default in the release version. Release exec jar size changed from the >> original 57M to 74.5M >> >> Compile parameter -Pspring-cloud-eureka will be discarded, To enable the >> Eureka Discovery Client, you can set eureka.client.enabled=true, This allows >> the user to experience it quickly. >> >> Support spring cloud eureka 1.x and 2.x at the same time, spring cloud >> eureka 2.x by default, you can be use profile build switch 1.x, I want to >> consider module splitting after implementing this feature >> >> Any suggestions >> >> >> >> coolbeevip >> >> BOCO >> >> >> >>> 在 2019年2月25日，下午7:21，Willem Jiang 写道： >>> >>> sounds good. >>> I just have one more question, when we build the alpha-server which >>> starter would be used by default? >>> >>> Willem Jiang >>> >>> Twitter: willemjiang >>> Weibo: 姜宁willem >>> >>> On Mon, Feb 25, 2019 at 6:17 PM zhang_...@boco.com.cn >>> wrote: >>>> >>>> The alpha-spring-boot-compatibility module now contains the dependencies >>>> of spring cloud eureka. I want to do the following refactoring >>>> >>>> 1. Remove spring-cloud-starter-netflix-eureka-client dependency from the >>>> alpha-spring-boot-compatibility module >>>> 2. Add alpha-starter-eureka model and added >>>> spring-cloud-starter-netflix-eureka-client dependency >>>> 3. Add a profile for alpha-starter-eureka module reference >>>> 4. Other support modules in the future can also use the naming convention >>>> alpha-starter-xxx, for example alpha-starter-consul >>>> >>>> Any suggestions? >>>> >>>> coolbeevip >>>> >>>> BOCO >>>> >>>> >>>> >>
Re: [discuss][pack]About Alpha module naming
Solution about https://issues.apache.org/jira/browse/SCB-1180 We can include spring-cloud-starter-netflix-eureka-client dependencies by default in the release version. Release exec jar size changed from the original 57M to 74.5M Compile parameter -Pspring-cloud-eureka will be discarded, To enable the Eureka Discovery Client, you can set eureka.client.enabled=true, This allows the user to experience it quickly. Support spring cloud eureka 1.x and 2.x at the same time, spring cloud eureka 2.x by default, you can be use profile build switch 1.x, I want to consider module splitting after implementing this feature Any suggestions coolbeevip BOCO > 在 2019年2月25日，下午7:21，Willem Jiang 写道： > > sounds good. > I just have one more question, when we build the alpha-server which > starter would be used by default? > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Feb 25, 2019 at 6:17 PM zhang_...@boco.com.cn > wrote: >> >> The alpha-spring-boot-compatibility module now contains the dependencies of >> spring cloud eureka. I want to do the following refactoring >> >> 1. Remove spring-cloud-starter-netflix-eureka-client dependency from the >> alpha-spring-boot-compatibility module >> 2. Add alpha-starter-eureka model and added >> spring-cloud-starter-netflix-eureka-client dependency >> 3. Add a profile for alpha-starter-eureka module reference >> 4. Other support modules in the future can also use the naming convention >> alpha-starter-xxx, for example alpha-starter-consul >> >> Any suggestions? >> >> coolbeevip >> >> BOCO >> >> >>
Re: [discuss][pack]About Alpha module naming
It is indeed a problem As a user, I always need to integrate with existing microservices frameworks，Maybe it's a discovery service or a security framework or a tracking service… Maybe we can write a project creation guide to how to create your own alpha service using this alpha-based dependency package，same spring cloud projects。 coolbeevip BOCO > 在 2019年2月25日，下午7:21，Willem Jiang 写道： > > sounds good. > I just have one more question, when we build the alpha-server which > starter would be used by default? > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Feb 25, 2019 at 6:17 PM zhang_...@boco.com.cn > wrote: >> >> The alpha-spring-boot-compatibility module now contains the dependencies of >> spring cloud eureka. I want to do the following refactoring >> >> 1. Remove spring-cloud-starter-netflix-eureka-client dependency from the >> alpha-spring-boot-compatibility module >> 2. Add alpha-starter-eureka model and added >> spring-cloud-starter-netflix-eureka-client dependency >> 3. Add a profile for alpha-starter-eureka module reference >> 4. Other support modules in the future can also use the naming convention >> alpha-starter-xxx, for example alpha-starter-consul >> >> Any suggestions? >> >> coolbeevip >> >> BOCO >> >> >>
[discuss][pack]About Alpha module naming
The alpha-spring-boot-compatibility module now contains the dependencies of spring cloud eureka. I want to do the following refactoring 1. Remove spring-cloud-starter-netflix-eureka-client dependency from the alpha-spring-boot-compatibility module 2. Add alpha-starter-eureka model and added spring-cloud-starter-netflix-eureka-client dependency 3. Add a profile for alpha-starter-eureka module reference 4. Other support modules in the future can also use the naming convention alpha-starter-xxx, for example alpha-starter-consul Any suggestions? coolbeevip BOCO
What protocol is used to access http://${alpha-server:port}/events
“Then you can start your micro-services and access all saga events via
http://${alpha-server:port}/events. ” ,The description in the user_guide.md
What protocol? gRPC or RESTful
coolbeevip
BOCO
Re: [DISCUSSION]No need to rebuild the way to let alpha support multiple database types
I have modified the docs/faq/cn/how_to_use_mysql_as_alpha_backend_database.md file in https://github.com/apache/servicecomb-pack/pull/405, Do I need to wait for this PR to be merged into the master after submitting new PR? 张 磊 部门: 亿阳信通IT运维支撑产品线 地址: 北京市海淀区杏石口路99号西山赢府商务中心2410 邮编: 100093 手机: 18610099300 移邮：zhang_...@boco.com.cn > 在 2019年2月17日，下午10:42，Willem Jiang 写道： > > It's good solution, but due to license issue, we cannot ship the MySQL > binary jars in our convenience binary release. > But We could update the FAQ document for it. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Sun, Feb 17, 2019 at 12:24 AM zhang_...@boco.com.cn > wrote: >> >> We can use loads external jars support multiple database types >> create libs directory in the alpha-server-0.4.0-SNAPSHOT-exec.jar >> directory, copy mysql-connector-java-8.0.15.jar to the libs directory And >> add config -Dloader.path=./libs to the command line, e.g. >> >> java -Dloader.path=./libs -jar alpha-server-0.4.0-SNAPSHOT-exec.jar \ >> --spring.datasource.platform=mysql \ >> --spring.datasource.dataSourceClassName=com.mysql.jdbc.Driver \ >> --spring.datasource.url='jdbc:mysql://0.0.0.0:3306/saga?useUnicode=true=utf-8=true' >> \ >> --spring.datasource.username=saga-user \ >> --spring.datasource.password=saga-password \ >> --spring.profiles.active=prd >> >> In order to external jars support need to use `ZIP` layout in maven plugin >> configuration, e.g >> >> >> org.springframework.boot >> spring-boot-maven-plugin >> >> ZIP >> >> >> >> coolbeevip >> >> BOCO >> >> >>
[DISCUSSION]No need to rebuild the way to let alpha support multiple database types
We can use loads external jars support multiple database types create libs directory in the alpha-server-0.4.0-SNAPSHOT-exec.jar directory, copy mysql-connector-java-8.0.15.jar to the libs directory And add config -Dloader.path=./libs to the command line, e.g. java -Dloader.path=./libs -jar alpha-server-0.4.0-SNAPSHOT-exec.jar \ --spring.datasource.platform=mysql \ --spring.datasource.dataSourceClassName=com.mysql.jdbc.Driver \ --spring.datasource.url='jdbc:mysql://0.0.0.0:3306/saga?useUnicode=true=utf-8=true' \ --spring.datasource.username=saga-user \ --spring.datasource.password=saga-password \ --spring.profiles.active=prd In order to external jars support need to use `ZIP` layout in maven plugin configuration, e.g org.springframework.boot spring-boot-maven-plugin ZIP coolbeevip BOCO
[discuss] Use random port when configuring alpha.server.port=0
When alpha is used in conjunction with Eureka, Omega can get the Alpha gRPC port from Eureka, so use random port when configuring alpha.server.port=0 We don't have to plan ports when alpha dynamic scaling any suggestion? coolbeevip BOCO
Re: Spring boot version compatibility issue when using actuator in Alpha
Do not worry that the shutdown interface can be enabled by the startup parameter only when the acceptance test 张 磊 部门: 亿阳信通IT运维支撑产品线 地址: 北京市海淀区杏石口路99号西山赢府商务中心2410 邮编: 100093 手机: 18610099300 移邮：zhang_...@boco.com.cn > 在 2019年2月1日，下午2:04，Willem Jiang 写道： > > It sounds good to me, please go ahead. > As the start, stop the alpha server is quit important in the > production environment, we need to make sure the restful management > API is protected in the production model.
Re: Spring boot version compatibility issue when using actuator in Alpha
I need to stop the Master node during the acceptance test of the Alpha cluster
mode, It test the slave node can automatically switch to the master status. So
I need to know Alpha state is Master or Slave, I want to use the custom
actuator endpoint to implement the Alpha state query interface.
> My question is how can you tell Alpha which kind of Actuator(Spring
> Boot 1.x or Spring Boot 2.x) you want to use.
Configured by profile (e.g -Pspring-boot-1 or -Pspring-boot-2 ) when building
Alpha Server
张 磊
部门: 亿阳信通IT运维支撑产品线
地址: 北京市海淀区杏石口路99号西山赢府商务中心2410
邮编: 100093
手机: 18610099300
移邮：zhang_...@boco.com.cn
> 在 2019年1月31日，下午9:03，Willem Jiang 写道：
>
> Hi,
>
> You don't need to pass all the code here. You can show your proposal
> by telling us what you want to do with Actuator.
> My question is how can you tell Alpha which kind of Actuator(Spring
> Boot 1.x or Spring Boot 2.x) you want to use.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Thu, Jan 31, 2019 at 1:40 PM wrote:
>>
>> 1. I want to extend management based on Actuator in Alpha，But the custom of
>> Actuator is not compatible in spring boot 1.x and spring boot 2.x
>> I think it can be solved by adding alpha-spring-boot-compatibility module,
>> alpha-spring-boot-compatibility contains alpha-spring-boot-1-starter and
>> alpha-spring-boot-2-starter.
>>
>>
>> Customize Alpha Endpoint in spring boot 1.x
>> package org.apache.servicecomb.pack.alpha.server.actuate.endpoint;
>>
>> import org.apache.servicecomb.pack.alpha.core.NodeStatus;
>> import org.apache.servicecomb.pack.alpha.core.actuate.endpoint.AlphaStatus;
>> import org.springframework.boot.actuate.endpoint.Endpoint;
>> import org.springframework.boot.context.properties.ConfigurationProperties;
>> import org.springframework.stereotype.Component;
>>
>> @ConfigurationProperties(prefix = "endpoints.alpha")
>> @Component
>> public class AlphaEndpoint implements Endpoint {
>>
>> public static final String END_POINT_ID = "alpha";
>>
>> private AlphaStatus alphaStatus = new AlphaStatus();
>>
>> @Override
>> public String getId() {
>>return END_POINT_ID;
>> }
>>
>> @Override
>> public boolean isEnabled() {
>>return true;
>> }
>>
>> @Override
>> public boolean isSensitive() {
>>return false;
>> }
>>
>> @Override
>> public AlphaStatus invoke() {
>>alphaStatus.setNodeType(NodeStatus.TypeEnum.MASTER);
>>return alphaStatus;
>> }
>>
>> }
>>
>>
>> Customize Alpha Endpoint in spring boot 2.x
>> package org.apache.servicecomb.pack.alpha.server.actuate.endpoint;
>>
>> import org.apache.servicecomb.pack.alpha.core.NodeStatus;
>> import org.apache.servicecomb.pack.alpha.core.actuate.endpoint.AlphaStatus;
>> import org.springframework.boot.actuate.endpoint.annotation.Endpoint;
>> import org.springframework.boot.actuate.endpoint.annotation.ReadOperation;
>> import org.springframework.context.annotation.Configuration;
>>
>>
>> @Configuration
>> @Endpoint(id = "alpha")
>> public class AlphaEndPoint {
>>
>> private AlphaStatus alphaStatus = new AlphaStatus();
>>
>> @ReadOperation
>> public AlphaStatus endpoint() {
>>alphaStatus.setNodeType(NodeStatus.TypeEnum.MASTER);
>>return alphaStatus;
>> }
>> }
>>
>>
>> Add dependencies in Alpha server，it version same ${spring.boot.version}
>>
>> org.apache.servicecomb.pack
>> alpha-spring-boot-starter
>> ${spring.boot.version}
>>
>>
>> 2. Additional features
>> Same Actuator Endpoint access path with spring boot 1.x and spring boot 2.x
>> Customized ActuatorEndpoint compatible spring boot 2.x actuator in spring
>> boot 1.x, You can access it via http://127.0.0
>> <http://127.0.0/>.1/actuator/xxx when using spring boot 1.x
>>
>> Define ActuatorEndpoint class
>> package org.apache.servicecomb.pack.alpha.server.actuate.endpoint;
>>
>> import org.springframework.beans.factory.annotation.Autowired;
>> import org.springframework.boot.actuate.endpoint.Endpoint;
>> import org.springframework.stereotype.Component;
>>
>> import java.util.List;
>>
>> @Component
>> public class ActuatorEndpoint implements Endpoint> {
>>
>> @Autowired
>> private List endpoints;
>>
>> @Override
>> public String getId() {
>>return "ac
