servicecomb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Willem Jiang <willem.ji...@gmail.com>
Subject Re: [VOTE] Release Apache ServiceComb Pack version 0.4.0 (RC-02)
Date Fri, 05 Apr 2019 08:56:57 GMT
As we have the accept test to verify the artifacts, I think there may
have two version of Omega context in your class path.
 Can you double check it?

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Fri, Apr 5, 2019 at 4:51 PM bismy <bismy@qq.com> wrote:
>
> I tried following command and resolved the problem:
>
> java -Dspring.profiles.active=mysql -Dloader.path=./libs -Dalpha.server.host=0.0.0.0
-Dalpha.server.port=7080 -Dserver.port=6090 -Dalpha.cluster.address=localhost:7080 -D"spring.datasource.url=jdbc:mysql://localhost:3306/saga?useSSL=false&serverTimezone=Asia/Shanghai&characterEncoding=utf8"
-Dspring.datasource.username=root -Dspring.datasource.password=root -jar alpha-server-0.4.0-exec.jar
>
> Some problems I met when I try to running alpha, I attached to the mail. Some configurations
are not mentioned in docs, so it takes quite  an effort to fix it.
>
> Now I meed another problem, after I changing omega from 0.3.0 to 0.4.0, I got following
error ( demo is here: https://github.com/huaweicse/cse-java-chassis-samples/tree/master/HouseAppWithSpringBoot2).
>
> 2019-04-04 15:54:45.179  INFO 5668 --- [ntloop-thread-0] c.h.p.f.auth.credentials.AKSKManager
    : The application missing project infomation, so choose a nearest one [cn-north-1]
> 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: {}
>         at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:732)
>         at 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_lei@boco.com.cn"<zhang_lei@boco.com.cn>;
> 发送时间: 2019年4月4日(星期四) 下午3:42
> 收件人: "dev"<dev@servicecomb.apache.org>;
> 主题: 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&useSSL=false"
\
> --spring.datasource.username=saga-user \
> --spring.datasource.password=saga-password
>
>
> > 在 2019年4月4日,下午3:20,bismy <bismy@qq.com> 写道:
> >
> > 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=xxxx -Dspring.datasource.password=xxxx -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"<asifdxtreme@apache.org>;
> > 发送时间: 2019年4月3日(星期三) 下午5:50
> > 收件人: "dev"<dev@servicecomb.apache.org>;
> > 抄送: "vinaym"<vinaym@huawei.com>; "krishna.m.kumar"<krishna.m.kumar@huawei.com>;
> > 主题: Re: [VOTE] Release Apache ServiceComb Pack version 0.4.0 (RC-02)
> >
> >
> >
> > +1 binding
> >
> > Checks Done:
> > - Hashes and Signature is good
> > - Archive matching the Git tag
> > - LICENSE, NOTICE exist
> > - ASF headers present in relevant files
> > - mvn clean install
> >
> > Regards
> > Asif
> >
> > On Wed, Apr 3, 2019 at 1:42 PM Willem Jiang <willem.jiang@gmail.com> wrote:
> >
> >> +1.
> >>
> >> The git tag is right, and commits has the latest fix of issue we found
> >> in last round release.
> >> I verified the staging repo by running the demo test against it.
> >> The release kits looks good to me.
> >>
> >> Willem Jiang
> >>
> >> Twitter: willemjiang
> >> Weibo: 姜宁willem
> >>
> >> On Tue, Apr 2, 2019 at 6:23 AM Mohammad Asif Siddiqui
> >> <asifdxtreme@apache.org> wrote:
> >>>
> >>> Hi All,
> >>>
> >>> This is a call for Vote to release Apache ServiceComb Pack version 0.4.0
> >> (RC-02)
> >>>
> >>> Release Candidate :
> >> https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-pack/0.4.0/rc-02/
> >>>
> >>> Staging Repository :
> >> https://repository.apache.org/content/repositories/orgapacheservicecomb-1380
> >>>
> >>> Release Tag :
> >> https://github.com/apache/servicecomb-pack/releases/tag/0.4.0
> >>>
> >>> Release CommitID : c2b1a6d603b0fb3d658a495da29d6f864995b538
> >>>
> >>> Release Notes :
> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626&version=12344102
> >>>
> >>> Keys to verify the Release Candidate :
> >> https://dist.apache.org/repos/dist/dev/servicecomb/KEYS
> >>>
> >>> Voting will start now ( Tuesday, 2nd April, 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
>
> Thanks,
> Zhang Lei.
>
>
>

Mime
View raw message