In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-31 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Development >
Share
Shulou(Shulou.com)06/01 Report--
This article mainly explains "springBoot integration Eureka startup failure how to solve", the article explains the content is simple and clear, easy to learn and understand, now please follow the editor's train of thought slowly in depth, together to study and learn "springBoot integration Eureka startup failure how to solve" it!
In fact, it is relatively simple for springBoot to integrate Eureka, but I find that many people will not be able to start after integration. Here are some common reasons for reporting errors.
Report: A child container failed during start
As shown in the picture
The reason for this is that pom.xml did not add
Org.springframework.cloud spring-cloud-dependencies Finchley.SR1 pom import
If you still report an error after adding:
The reason for the error is that Springboot and SpringCloud versions do not match.
After the modification, it will work normally! Finally, post their corresponding version, and you can watch the corresponding springboot version change springCloud.
Spring Boot Spring Cloud
1.2.x Angel version
1.3.x Brixton version
1.4.x stripes Camden version
1.5.x Dalston version, Edgware version
Version 2.0.x Finchley
SpringCloud exception (Euruka)
Application run failed java.lang.NoSuchMethodError: org.springframework.boot.builder.SpringApplicationBuilder
This problem was encountered while testing Euruka as a service registry. The error message is as follows:
"C:\ Program Files\ Java\ jdk1.8.0_161\ bin\ java"-XX:TieredStopAtLevel=1 -. Com.fangxing.springcloud.eurukaserver.EurukaServerApplication15:04:35.690 [main] DEBUG org.springframework.boot.context.logging.ClasspathLoggingApplicationListener-Application failed to start with classpath:. File:/D:/Program%20Files/JetBrains/IntelliJ%20IDEA%202017.3.5/lib/idea_rt.jar [background-preinit] DEBUG org.jboss.logging-Logging Provider: org.jboss.logging.Log4j2LoggerProvider15:04:35.869 [background-preinit] INFO org.hibernate.validator.internal.util.Version-HV000001: Hibernate Validator 6.0.7.Final15:04:35.884 [background-preinit] DEBUG org.hibernate.validator.internal.engine.resolver.TraversableResolvers-Cannot find javax.persistence.Persistence on classpath. Assuming non JPA 2 environment. All properties will per default be traversable.15:04:35.890 [background-preinit] DEBUG org.hibernate.validator.internal.xml.ValidationXmlParser-Trying to load META-INF/validation.xml for XML based Validator configuration.15:04:35.892 [background-preinit] DEBUG org.hibernate.validator.internal.xml.ResourceLoaderHelper-Trying to load META-INF/validation.xml via TCCL15:04:35.893 [background-preinit] DEBUG org.hibernate.validator.internal.xml.ResourceLoaderHelper-Trying to load META-INF/validation.xml Via Hibernate Validator's class loader15:04:35.894 [background-preinit] DEBUG org.hibernate.validator.internal.xml.ValidationXmlParser-No META-INF/validation.xml found. Using annotation based configuration only.15:04:36.086 [background-preinit] DEBUG org.hibernate.validator.messageinterpolation.ResourceBundleMessageInterpolator-Loaded expression factory via original TCCL15:04:36.090 [background-preinit] DEBUG org.hibernate.validator.internal.engine.ValidatorFactoryImpl-HV000234: Using org.hibernate.validator.messageinterpolation.ResourceBundleMessageInterpolator as ValidatorFactory-scoped message interpolator.15:04:36.090 [background-preinit] DEBUG org.hibernate.validator.internal.engine.ValidatorFactoryImpl-HV000234: Using org.hibernate.validator.internal.engine.resolver.TraverseAllTraversableResolver as ValidatorFactory-scoped traversable resolver.15:04:36.090 [background-preinit] DEBUG org.hibernate.validator.internal.engine.ValidatorFactoryImpl-HV000234: Using org.hibernate.validator.internal.util.ExecutableParameterNameProvider as ValidatorFactory-scoped parameter name provider.15:04:36.090 [background-preinit] DEBUG org.hibernate.validator.internal.engine.ValidatorFactoryImpl-HV000234: Using org.hibernate.validator.internal.engine.DefaultClockProvider as ValidatorFactory-scoped clock provider.15:04:36.090 [background-preinit] DEBUG org.hibernate.validator.internal. Engine.ValidatorFactoryImpl-HV000234: Using org.hibernate.validator.internal.engine.scripting.DefaultScriptEvaluatorFactory as ValidatorFactory-scoped script evaluator factory.15:04:36.404 [main] ERROR org.springframework.boot.SpringApplication-Application run failedjava.lang.NoSuchMethodError: org.springframework.boot.builder.SpringApplicationBuilder. ([Ljava/lang/Object ) V at org.springframework.cloud.bootstrap.BootstrapApplicationListener.bootstrapServiceContext (BootstrapApplicationListener.java:120) at org.springframework.cloud.bootstrap.BootstrapApplicationListener.onApplicationEvent (BootstrapApplicationListener.java:84) at org.springframework.cloud.bootstrap.BootstrapApplicationListener.onApplicationEvent (BootstrapApplicationListener.java:62) at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener (SimpleApplicationEventMulticaster.java:172) at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener (SimpleApplicationEventMulticaster.java:165) at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent (SimpleApplicationEventMulticaster.java:139) at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent (SimpleApplicationEventMulticaster.java:127) at org.springframework.boot.context.event.EventPublishingRunListener.environmentPrepared (EventPublishingRunListener.java:74) at org.springframework.boot.SpringApplicationRunListeners.environmentPrepared (SpringApplicationRunListeners.java:54) at org.springframework.boot.SpringApplication.prepareEnvironment (SpringApplication.java:351) at org.springframework.boot.SpringApplication.run (SpringApplication.java:317) at org.springframework.boot.SpringApplication.run (SpringApplication.java:1246) at org.springframework.boot.SpringApplication.run (SpringApplication.java:1234) at com.fangxing.springcloud.eurukaserver.EurukaServerApplication.main (EurukaServerApplication.java:16) Process finished with exit code 1
The root cause is the version conflict of the dependent package. My pom.xml file is as follows:
4.0.0 com.fangxing.springcloud euruka-server 0.0.1-SNAPSHOT jar euruka-server Demo project for Eureka Server org.springframework.boot spring-boot-starter-parent 2.0.0.RELEASE UTF-8 UTF-8 1.8 org.springframework.boot spring-boot-starter -web org.springframewor k.boot spring-boot-starter-test test org.springframework.cloud spring-cloud-starter-eureka-server org.springframework.cloud spring-cloud-dependencies Camden.SR3 pom import org.springframework.boot spring-boot-maven-plugin
The version of SpringBoot used here is version 2.0.0.0. Let's adjust the version and use the following pom.xml
4.0.0 com.fangxing.springcloud euruka-server 0.0.1-SNAPSHOT jar euruka-server Demo project for Eureka Server org.springframework.boot spring-boot-starter-parent 1.4.0.RELEASE UTF-8 1.8 org.springframework.cloud spring- Cloud-starter-eureka-server org.springframework.boot spring-boot-starter-test test org.springframework.cloud spring-cloud-dependencies Camden.SR3 pom import Org.springframework.boot spring-boot-maven-plugin
Enable normal.
Thank you for your reading, the above is the content of "springBoot integration Eureka startup failure how to solve", after the study of this article, I believe you have a deeper understanding of springBoot integration Eureka startup failure how to solve this problem, the specific use of the situation also needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.