spring-cloud启动报错
spring-cloud启动报错
- `Connected to the target VM, address: '127.0.0.1:2763', transport: 'socket'
`Connected to the target VM, address: ‘127.0.0.1:2763’, transport: ‘socket’
2019-10-06 16:30:39 [ main:0 ] - [ INFO ] org.springframework.context.support.AbstractApplicationContext.prepareRefresh(AbstractApplicationContext.java:590) Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@2ea6e30c: startup date [Sun Oct 06 16:30:39 CST 2019]; root of context hierarchy
2019-10-06 16:30:40 [ main:307 ] - [ INFO ] org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.(AutowiredAnnotationBeanPostProcessor.java:153) JSR-330 ‘javax.inject.Inject’ annotation found and supported for autowiring
2019-10-06 16:30:40 [ main:361 ] - [ INFO ] org.springframework.context.support.PostProcessorRegistrationDelegate B e a n P o s t P r o c e s s o r C h e c k e r . p o s t P r o c e s s A f t e r I n i t i a l i z a t i o n ( P o s t P r o c e s s o r R e g i s t r a t i o n D e l e g a t e . j a v a : 326 ) B e a n ′ c o n f i g u r a t i o n P r o p e r t i e s R e b i n d e r A u t o C o n f i g u r a t i o n ′ o f t y p e [ o r g . s p r i n g f r a m e w o r k . c l o u d . a u t o c o n f i g u r e . C o n f i g u r a t i o n P r o p e r t i e s R e b i n d e r A u t o C o n f i g u r a t i o n BeanPostProcessorChecker.postProcessAfterInitialization(PostProcessorRegistrationDelegate.java:326) Bean 'configurationPropertiesRebinderAutoConfiguration' of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration BeanPostProcessorChecker.postProcessAfterInitialization(PostProcessorRegistrationDelegate.java:326)Bean′configurationPropertiesRebinderAutoConfiguration′oftype[org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration E n h a n c e r B y S p r i n g C G L I B EnhancerBySpringCGLIB EnhancerBySpringCGLIB$281ce050] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2019-10-06 16:30:40.272 INFO 8736 — [ main] c.a.c.c.acm.AliCloudAcmInitializer : Initialize acm from acm configuration.
. ____ _ __ _ _
/\ / ’ __ _ () __ __ _ \ \ \
( ( )__ | '_ | '| | ’ / ` | \ \ \
\/ )| |)| | | | | || (| | ) ) ) )
’ || .__|| ||| |__, | / / / /
=|_|======|/=////
:: Spring Boot :: (v2.0.5.RELEASE)
Sun Oct 06 16:30:40 CST 2019 sun.misc.Launcher A p p C l a s s L o a d e r @ 14 d a d 5 d c J M . L o g : I N F O I n i t J M l o g g e r w i t h S l f 4 j L o g g e r F a c t o r y s u c c e s s , s u n . m i s c . L a u n c h e r AppClassLoader@14dad5dc JM.Log:INFO Init JM logger with Slf4jLoggerFactory success, sun.misc.Launcher AppClassLoader@14dad5dcJM.Log:INFOInitJMloggerwithSlf4jLoggerFactorysuccess,sun.misc.LauncherAppClassLoader@14dad5dc
Sun Oct 06 16:30:40 CST 2019 sun.misc.LauncherKaTeX parse error: Undefined control sequence: \Users at position 54: …g root path: C:\̲U̲s̲e̲r̲s̲\GL17080010\log…AppClassLoader@14dad5dc JM.Log:INFO Set nacos log path: C:\Users\GL17080010\logs\nacos
2019-10-06 16:30:40.626 ERROR 8736 — [ main] o.s.c.a.nacos.NacosConfigProperties : create config service error!properties=NacosConfigProperties{serverAddr=‘null’, encode=‘null’, group=‘DEFAULT_GROUP’, prefix=‘null’, fileExtension=‘properties’, timeout=3000, endpoint=‘null’, namespace=‘null’, accessKey=‘null’, secretKey=‘null’, contextPath=‘null’, clusterName=‘null’, name=‘scorpio’, activeProfiles=[]},e=,
com.alibaba.nacos.api.exception.NacosException: null
at com.alibaba.nacos.api.config.ConfigFactory.createConfigService(ConfigFactory.java:48) ~[nacos-api-0.3.0.jar:na]
at com.alibaba.nacos.api.NacosFactory.createConfigService(NacosFactory.java:44) ~[nacos-api-0.3.0.jar:na]
at org.springframework.cloud.alibaba.nacos.NacosConfigProperties.configServiceInstance(NacosConfigProperties.java:265) ~[spring-cloud-alibaba-nacos-config-0.2.0.RELEASE.jar:0.2.0.RELEASE]
at org.springframework.cloud.alibaba.nacos.client.NacosPropertySourceLocator.locate(NacosPropertySourceLocator.java:52) [spring-cloud-alibaba-nacos-config-0.2.0.RELEASE.jar:0.2.0.RELEASE]
at org.springframework.cloud.bootstrap.config.PropertySourceBootstrapConfiguration.initialize(PropertySourceBootstrapConfiguration.java:94) [spring-cloud-context-2.0.1.RELEASE.jar:2.0.1.RELEASE]
at org.springframework.boot.SpringApplication.applyInitializers(SpringApplication.java:654) [spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
at org.springframework.boot.SpringApplication.prepareContext(SpringApplication.java:390) [spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:331) [spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1277) [spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1265) [spring-boot-2.0.5.RELEASE.jar:2.0.5.RELEASE]
at io.wharfoo.biztier.scorpio.Application.main(Application.java:69) [classes/:na]
2019-10-06 16:30:40 [ main:799 ] - [ ERROR ] org.springframework.boot.diagnostics.LoggingFailureAnalysisReporter.report(LoggingFailureAnalysisReporter.java:42)
APPLICATION FAILED TO START
Description:
An attempt was made to call the method com.taobao.diamond.client.impl.DiamondEnvRepo.getDefaultEnv()Lcom/taobao/diamond/client/impl/DiamondEnv; but it does not exist. Its class, com.taobao.diamond.client.impl.DiamondEnvRepo, is available from the following locations:
jar:file:/D:/Java/repository/com/taobao/diamond/diamond-client/edas-3.7.3/diamond-client-edas-3.7.3.jar!/com/taobao/diamond/client/impl/DiamondEnvRepo.class
jar:file:/D:/Java/repository/com/alibaba/edas/acm/acm-sdk/1.0.8/acm-sdk-1.0.8.jar!/com/taobao/diamond/client/impl/DiamondEnvRepo.class
It was loaded from the following location:
file:/D:/Java/repository/com/taobao/diamond/diamond-client/edas-3.7.3/diamond-client-edas-3.7.3.jar
Action:
Correct the classpath of your application so that it contains a single, compatible version of com.taobao.diamond.client.impl.DiamondEnvRepo
Disconnected from the target VM, address: ‘127.0.0.1:2763’, transport: ‘socket’
Process finished with exit code 1`