Re: [VOTE] Release Apache ServiceComb Pack version 0.4.0 (RC-02)
When starting the alpha server, it don't need to use the OmegaContext.
It looks like there are some setting error in your class path.
Willem Jiang
Twitter: willemjiang
Weibo: 姜宁willem
On Thu, Apr 4, 2019 at 3:21 PM bismy wrote:
>
> 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 loaded
> because @ConditionalOnProperty (alpha.cluster.address) did
Re: [PROPOSAL] ServiceComb MetaConfig
does it support multiple cluster configurations management?? -- Original -- From: wjm wjm Date: Thu,Apr 4,2019 4:41 PM To: dev Subject: Re: [PROPOSAL] ServiceComb MetaConfig do we have a mechanism to use the configuration with high performance?? Xiaoliang Tian ??2019??3??29?? 5:27?? > sure, mainly forcus on management , ease of use, rollback, key value > version control. value validation. > > first we support API, later UX. > > bismy ??2019??3??29?? 4:08?? > > > Provide a centered configuration management service is very important for > > ServiceComb, because all microservice governance functions are based on > > dynamic properties. In ServiceComb microservice view, now we currently > use > > following functions( implement archaius api using apollo and > config-center) > > > > > > * pull/push configurations of key-value pair from configuration > service. > > > > > > in microservice view, no future functions is needed. So I guess the > > suggested service mainly focus on management functions. How do you decide > > to provide this functions? Add a management console or by REST api? > > > > > > -- -- > > ??: "Xiaoliang Tian"; > > : 2019??3??29??(??) 2:14 > > ??: "dev"; > > > > : Re: [PROPOSAL] ServiceComb MetaConfig > > > > > > > > let's think how we change a timeout for a particular operation? > > the key is xxx.usermanagement.user.getuser.timeout, is that key easy to > be > > manged by operator? I guess he has to learn a special key rule only make > > sense in his team > > > > I want this timeout just be timeout, and easy to read > > it bacame timeout(service= usermanagement , > schema=user,opertion=getuser) > > > > Xiaoliang Tian ??2019??3??29?? > > 12:15?? > > > > > > > > maybe the name confused??it is a service only for configurations??but the > > key contains metadata > > > key1: log_level(service=cart, version=1.0, app=mall) > > > key2: log_level(service=cart, version=1.0, app=mall, ip=x.x.x.x) > > > that is 2 different keys > > > > > > you can consider apollo has fixed metadata and one fixed view to math > > > their own scenario. > > > > > > but in apollo, key can be very complicated, user can not easily > observe > > > keys, a lot of metadata will be attacted to key name, just like ip to > > > "log_level" > > > > > > Willem Jiang ??2019??3??29?? 11:36?? > > > > > >> Hi Xiaoliang, > > >> > > >> Do you propose we start a new project to manage the micro services > meta > > >> datas? > > >> Currently we just have a solution to integrate with with Apollo for > > >> configuration management, but what's the difference between the > > >> service metadata and configuration? > > >> I could help us to understand the proposal, if we can drop a clear > line > > >> for it. > > >> > > >> > > >> Willem Jiang > > >> > > >> Twitter: willemjiang > > >> Weibo: willem > > >> > > >> On Fri, Mar 29, 2019 at 10:52 AM Xiaoliang Tian > > >> wrote: > > >> > > > >> > MetaConfig is a service for configuration management in an large > > >> scaled > > >> > distrbuted system. > > >> > > > >> > Currently we use ctrip appllo for config managment, but it is build > > for > > >> a > > >> > paticular scenario. it has fixed schema > > >> application,environment,cluster and > > >> > namespace. Each key belong to that schema. > > >> > > > >> > But it is not enough for operator to manage a complicated > > >> infrasctructure > > >> > or application cluster. > > >> > > > >> > So here is the proposal to build a brand new config management > > service, > > >> > > > >> > *Features: * > > >> > *key with rich metadata: *user can define metadata for a key , that > > >> > distinguish from key to another key. a key will not be stringed by > > >> fixed > > >> > schema. metadata is like "env=test, service=cart, version=1.0" or > > >> > "cluster=xxx" or "env=test, service=cart, version=1.0, ip=x.x.x.x" > > >> > *validator: *value can be checked by user defined python script, so > in > > >> > runtine if someone want to change this value, the script will check > if > > >> this > > >> > value is properate. > > >> > *encryption webhook: *. value can by ecrypt by your custom > encryption > > >> > service. > > >> > *event producer: *producer will send key changes event to a target > > >> > service(kafka,rabbitmq, customed). > > >> > *config view: *by setting metadata criteria, MetaConfig will > > aggregate a > > >> > view to return all key values which match those metadata, so that > > >> operator > > >> > can mange key in their own understading to a distributed system in > > >> > seperated views. > > >> > *config batch action: * with metadate, you can batch update, delete > > key > > >> > values. for example: update all "service=cart version=1.0" > > configuration > > >> > log level to "DEBUG" or just update "service=cart version=1.0, > > >> ip=x.x.x.x" > > >> > . > > >> >
Re: [PROPOSAL] ServiceComb MetaConfig
do we have a mechanism to use the configuration with high performance？ Xiaoliang Tian 于2019年3月29日周五 下午5:27写道： > sure, mainly forcus on management , ease of use, rollback, key value > version control. value validation. > > first we support API, later UX. > > bismy 于2019年3月29日周五 下午4:08写道： > > > Provide a centered configuration management service is very important for > > ServiceComb, because all microservice governance functions are based on > > dynamic properties. In ServiceComb microservice view, now we currently > use > > following functions( implement archaius api using apollo and > config-center) > > > > > > * pull/push configurations of key-value pair from configuration > service. > > > > > > in microservice view, no future functions is needed. So I guess the > > suggested service mainly focus on management functions. How do you decide > > to provide this functions? Add a management console or by REST api? > > > > > > -- 原始邮件 -- > > 发件人: "Xiaoliang Tian"; > > 发送时间: 2019年3月29日(星期五) 下午2:14 > > 收件人: "dev"; > > > > 主题: Re: [PROPOSAL] ServiceComb MetaConfig > > > > > > > > let's think how we change a timeout for a particular operation? > > the key is xxx.usermanagement.user.getuser.timeout, is that key easy to > be > > manged by operator? I guess he has to learn a special key rule only make > > sense in his team > > > > I want this timeout just be timeout, and easy to read > > it bacame timeout(service= usermanagement , > schema=user,opertion=getuser) > > > > Xiaoliang Tian 于2019年3月29日周五 下午12:15写道： > > > > > > > > maybe the name confused，it is a service only for configurations，but the > > key contains metadata > > > key1: log_level(service=cart, version=1.0, app=mall) > > > key2: log_level(service=cart, version=1.0, app=mall, ip=x.x.x.x) > > > that is 2 different keys > > > > > > you can consider apollo has fixed metadata and one fixed view to math > > > their own scenario. > > > > > > but in apollo, key can be very complicated, user can not easily > observe > > > keys, a lot of metadata will be attacted to key name, just like ip to > > > "log_level" > > > > > > Willem Jiang 于2019年3月29日周五 上午11:36写道： > > > > > >> Hi Xiaoliang, > > >> > > >> Do you propose we start a new project to manage the micro services > meta > > >> datas? > > >> Currently we just have a solution to integrate with with Apollo for > > >> configuration management, but what's the difference between the > > >> service metadata and configuration? > > >> I could help us to understand the proposal, if we can drop a clear > line > > >> for it. > > >> > > >> > > >> Willem Jiang > > >> > > >> Twitter: willemjiang > > >> Weibo: 姜宁willem > > >> > > >> On Fri, Mar 29, 2019 at 10:52 AM Xiaoliang Tian > > >> wrote: > > >> > > > >> > MetaConfig is a service for configuration management in an large > > >> scaled > > >> > distrbuted system. > > >> > > > >> > Currently we use ctrip appllo for config managment, but it is build > > for > > >> a > > >> > paticular scenario. it has fixed schema > > >> application,environment,cluster and > > >> > namespace. Each key belong to that schema. > > >> > > > >> > But it is not enough for operator to manage a complicated > > >> infrasctructure > > >> > or application cluster. > > >> > > > >> > So here is the proposal to build a brand new config management > > service, > > >> > > > >> > *Features: * > > >> > *key with rich metadata: *user can define metadata for a key , that > > >> > distinguish from key to another key. a key will not be stringed by > > >> fixed > > >> > schema. metadata is like "env=test, service=cart, version=1.0" or > > >> > "cluster=xxx" or "env=test, service=cart, version=1.0, ip=x.x.x.x" > > >> > *validator: *value can be checked by user defined python script, so > in > > >> > runtine if someone want to change this value, the script will check > if > > >> this > > >> > value is properate. > > >> > *encryption webhook: *. value can by ecrypt by your custom > encryption > > >> > service. > > >> > *event producer: *producer will send key changes event to a target > > >> > service(kafka,rabbitmq, customed). > > >> > *config view: *by setting metadata criteria, MetaConfig will > > aggregate a > > >> > view to return all key values which match those metadata, so that > > >> operator > > >> > can mange key in their own understading to a distributed system in > > >> > seperated views. > > >> > *config batch action: * with metadate, you can batch update, delete > > key > > >> > values. for example: update all "service=cart version=1.0" > > configuration > > >> > log level to "DEBUG" or just update "service=cart version=1.0, > > >> ip=x.x.x.x" > > >> > . > > >> > *rich value type: *not ony plain text any more, but support to be > > aware > > >> of > > >> > ini, json,yaml,xml and java properties > > >> > *heterogenous configuration system: *able to manage configuration in > > k8s > > >> > and consul or even more, you can update, delete, and use config
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
?????? [VOTE] Release Apache ServiceComb Pack version 0.4.0 (RC-02)
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 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.
-- --
??: "Mohammad Asif Siddiqui";
: 2019??4??3??(??) 5:50
??: "dev";
: "vinaym";
"krishna.m.kumar";
: Re: [VOTE] Release Apache ServiceComb Pack version 0.4.0
