1. 程式人生 > >SpringCloud客戶端Client啟動時自動停止

SpringCloud客戶端Client啟動時自動停止

報錯:
2018-05-30 18:07:35.436  INFO 7912 --- [           main] s.c.a.AnnotationConfigApplicationContext : Refreshing org.spring[email protected]20ce78ec: startup date [Wed May 30 18:07:35 CST 2018]; root of context hierarchy
2018-05-30 18:07:35.652  INFO 7912 --- [           main] f.a.AutowiredAnnotationBeanPostProcessor : JSR-330 'javax.inject.Inject' annotation found and supported for autowiring
2018-05-30 18:07:35.699  INFO 7912 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'configurationPropertiesRebinderAutoConfiguration' of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$a1cf77d7] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

 .   ____          _            __ _ _
/\\ / ___'_ __ _ _(_)_ __  __ _ \ \ \ \
( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \
\\/  ___)| |_)| | | | | || (_| |  ) ) ) )
 '  |____| .__|_| |_|_| |_\__, | / / / /
=========|_|==============|___/=/_/_/_/
:: Spring Boot ::        (v2.0.2.RELEASE)

2018-05-30 18:07:36.603  INFO 7912 --- [           main] com.zsl.client.ClientApplication         : No active profile set, falling back to default profiles: default
2018-05-30 18:07:36.616  INFO 7912 --- [           main] s.c.a.AnnotationConfigApplicationContext : Refreshing org.spring
[email protected]
198d6542: startup date [Wed May 30 18:07:36 CST 2018]; parent: org.spring[email protected]20ce78ec
2018-05-30 18:07:36.977  INFO 7912 --- [           main] o.s.cloud.context.scope.GenericScope     : BeanFactory id=c0d788a6-3698-3a44-a78c-18f4704863ee
2018-05-30 18:07:36.990  INFO 7912 --- [           main] f.a.AutowiredAnnotationBeanPostProcessor : JSR-330 'javax.inject.Inject' annotation found and supported for autowiring
2018-05-30 18:07:37.047  INFO 7912 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration' of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$a1cf77d7] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2018-05-30 18:07:37.155  WARN 7912 --- [           main] o.s.c.n.a.ArchaiusAutoConfiguration      : No spring.application.name found, defaulting to 'application'
2018-05-30 18:07:37.157  WARN 7912 --- [           main] c.n.c.sources.URLConfigurationSource     : No URLs will be polled as dynamic configuration sources.
2018-05-30 18:07:37.158  INFO 7912 --- [           main] c.n.c.sources.URLConfigurationSource     : To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
2018-05-30 18:07:37.162  WARN 7912 --- [           main] c.n.c.sources.URLConfigurationSource     : No URLs will be polled as dynamic configuration sources.
2018-05-30 18:07:37.162  INFO 7912 --- [           main] c.n.c.sources.URLConfigurationSource     : To enable URLs as dynamic configuration sources, define System property archaius.configurationSource.additionalUrls or make config.properties available on classpath.
2018-05-30 18:07:38.757  INFO 7912 --- [           main] o.s.j.e.a.AnnotationMBeanExporter        : Registering beans for JMX exposure on startup
2018-05-30 18:07:38.764  INFO 7912 --- [           main] o.s.j.e.a.AnnotationMBeanExporter        : Bean with name 'configurationPropertiesRebinder' has been autodetected for JMX exposure
2018-05-30 18:07:38.765  INFO 7912 --- [           main] o.s.j.e.a.AnnotationMBeanExporter        : Bean with name 'environmentManager' has been autodetected for JMX exposure
2018-05-30 18:07:38.765  INFO 7912 --- [           main] o.s.j.e.a.AnnotationMBeanExporter        : Bean with name 'refreshScope' has been autodetected for JMX exposure
2018-05-30 18:07:38.768  INFO 7912 --- [           main] o.s.j.e.a.AnnotationMBeanExporter        : Located managed bean 'environmentManager': registering with JMX server as MBean [org.springframework.cloud.context.environment:name=environmentManager,type=EnvironmentManager]
2018-05-30 18:07:38.780  INFO 7912 --- [           main] o.s.j.e.a.AnnotationMBeanExporter        : Located managed bean 'refreshScope': registering with JMX server as MBean [org.springframework.cloud.context.scope.refresh:name=refreshScope,type=RefreshScope]
2018-05-30 18:07:38.789  INFO 7912 --- [           main] o.s.j.e.a.AnnotationMBeanExporter        : Located managed bean 'configurationPropertiesRebinder': registering with JMX server as MBean [org.springframework.cloud.context.properties:name=configurationPropertiesRebinder,context=198d6542,type=ConfigurationPropertiesRebinder]
2018-05-30 18:07:38.797  INFO 7912 --- [           main] o.s.c.support.DefaultLifecycleProcessor  : Starting beans in phase 0
2018-05-30 18:07:38.805  INFO 7912 --- [           main] o.s.c.n.eureka.InstanceInfoFactory       : Setting initial instance status as: STARTING
2018-05-30 18:07:38.842  INFO 7912 --- [           main] com.netflix.discovery.DiscoveryClient    : Initializing Eureka in region us-east-1
2018-05-30 18:07:39.072  INFO 7912 --- [           main] c.n.d.provider.DiscoveryJerseyProvider   : Using JSON encoding codec LegacyJacksonJson
2018-05-30 18:07:39.072  INFO 7912 --- [           main] c.n.d.provider.DiscoveryJerseyProvider   : Using JSON decoding codec LegacyJacksonJson
2018-05-30 18:07:39.188  INFO 7912 --- [           main] c.n.d.provider.DiscoveryJerseyProvider   : Using XML encoding codec XStreamXml
2018-05-30 18:07:39.188  INFO 7912 --- [           main] c.n.d.provider.DiscoveryJerseyProvider   : Using XML decoding codec XStreamXml
2018-05-30 18:07:39.376  INFO 7912 --- [           main] c.n.d.s.r.aws.ConfigClusterResolver      : Resolving eureka endpoints via configuration
2018-05-30 18:07:39.763  INFO 7912 --- [           main] com.netflix.discovery.DiscoveryClient    : Disable delta property : false
2018-05-30 18:07:39.763  INFO 7912 --- [           main] com.netflix.discovery.DiscoveryClient    : Single vip registry refresh property : null
2018-05-30 18:07:39.764  INFO 7912 --- [           main] com.netflix.discovery.DiscoveryClient    : Force full registry fetch : false
2018-05-30 18:07:39.764  INFO 7912 --- [           main] com.netflix.discovery.DiscoveryClient    : Application is null : false
2018-05-30 18:07:39.764  INFO 7912 --- [           main] com.netflix.discovery.DiscoveryClient    : Registered Applications size is zero : true
2018-05-30 18:07:39.764  INFO 7912 --- [           main] com.netflix.discovery.DiscoveryClient    : Application version is -1: true
2018-05-30 18:07:39.764  INFO 7912 --- [           main] com.netflix.discovery.DiscoveryClient    : Getting all instance registry info from the eureka server
2018-05-30 18:07:39.916  INFO 7912 --- [           main] com.netflix.discovery.DiscoveryClient    : The response status is 200
2018-05-30 18:07:39.919  INFO 7912 --- [           main] com.netflix.discovery.DiscoveryClient    : Starting heartbeat executor: renew interval is: 30
2018-05-30 18:07:39.921  INFO 7912 --- [           main] c.n.discovery.InstanceInfoReplicator     : InstanceInfoReplicator onDemand update allowed rate per min is 4
2018-05-30 18:07:39.926  INFO 7912 --- [           main] com.netflix.discovery.DiscoveryClient    : Discovery Client initialized at timestamp 1527674859924 with initial instances count: 1
2018-05-30 18:07:39.930  INFO 7912 --- [           main] o.s.c.n.e.s.EurekaServiceRegistry        : Registering application unknown with eureka with status UP
2018-05-30 18:07:39.930  INFO 7912 --- [           main] com.netflix.discovery.DiscoveryClient    : Saw local status change event StatusChangeEvent [timestamp=1527674859930, current=UP, previous=STARTING]
2018-05-30 18:07:39.932  INFO 7912 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_UNKNOWN/OnePiece: registering service...
2018-05-30 18:07:39.948  INFO 7912 --- [           main] com.zsl.client.ClientApplication         : Started ClientApplication in 6.129 seconds (JVM running for 7.74)
2018-05-30 18:07:39.952  INFO 7912 --- [      Thread-18] s.c.a.AnnotationConfigApplicationContext : Closing org.spring
[email protected]
198d6542: startup date [Wed May 30 18:07:36 CST 2018]; parent: org.spring[email protected]20ce78ec
2018-05-30 18:07:39.953  INFO 7912 --- [      Thread-18] o.s.c.n.e.s.EurekaServiceRegistry        : Unregistering application unknown with eureka with status DOWN
2018-05-30 18:07:39.953  WARN 7912 --- [      Thread-18] com.netflix.discovery.DiscoveryClient    : Saw local status change event StatusChangeEvent [timestamp=1527674859953, current=DOWN, previous=UP]
2018-05-30 18:07:39.956  INFO 7912 --- [      Thread-18] o.s.c.support.DefaultLifecycleProcessor  : Stopping beans in phase 0
2018-05-30 18:07:39.958  INFO 7912 --- [      Thread-18] com.netflix.discovery.DiscoveryClient    : Shutting down DiscoveryClient ...
2018-05-30 18:07:39.974  INFO 7912 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_UNKNOWN/OnePiece - registration status: 204
2018-05-30 18:07:39.975  INFO 7912 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_UNKNOWN/OnePiece: registering service...
2018-05-30 18:07:39.981  INFO 7912 --- [nfoReplicator-0] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_UNKNOWN/OnePiece - registration status: 204
2018-05-30 18:07:39.982  INFO 7912 --- [      Thread-18] com.netflix.discovery.DiscoveryClient    : Unregistering ...
2018-05-30 18:07:39.989  INFO 7912 --- [      Thread-18] com.netflix.discovery.DiscoveryClient    : DiscoveryClient_UNKNOWN/OnePiece - deregister  status: 200
2018-05-30 18:07:39.999  INFO 7912 --- [      Thread-18] com.netflix.discovery.DiscoveryClient    : Completed shut down of DiscoveryClient
2018-05-30 18:07:40.000  INFO 7912 --- [      Thread-18] o.s.j.e.a.AnnotationMBeanExporter        : Unregistering JMX-exposed beans on shutdown
2018-05-30 18:07:40.000  INFO 7912 --- [      Thread-18] o.s.j.e.a.AnnotationMBeanExporter        : Unregistering JMX-exposed beans

Process finished with exit code 0
解決方法:
在pom.xml中加入
<dependency>  
   <groupId>org.springframework.boot</groupId>  
   <artifactId>spring-boot-starter-web</artifactId>  
</dependency>  
即可

相關推薦

SpringCloud客戶Client啟動自動停止

報錯:2018-05-30 18:07:35.436  INFO 7912 --- [           main] s.c.a.AnnotationConfigApplicationContext : Refreshing org.spring[email pr

CS7: 指定客戶加入域自動加入預定好的OU_方法1

nis dmi 客戶端 net pass netd .com ini main.c 客戶問題概括: 此問題為一面試官對筆者提問問題之一,問題為面試官有需求需要添加指定客戶端到預定好的域中。 答復: 可以使用兩種方法: A方法(針對Win7以上系統)netdom join C

idea新建的spring-cloud-eureka-client啟動自動停止

pom.xml檔案中新增 <!-- web應用 --> <dependency> <groupId>org.springframework.boot<

Android客戶首次啟動的引導介面(viewpager)

剛做完一個比賽專案,來寫點以後能用著的東西–Android客戶端的首次啟動頁面,而且這個以後複用的機率很大,也不怎麼修改,特留下為以後準備,同時為初學者提供一個幫助。 實現思路是:用SharedPreferences儲存一個首次登陸的資訊,預設是true,進入

zookeeper服務客戶啟動停止

zookeeper的命令列都位於專案目錄下的/bin/目錄下面,在執行這行命令前,我們首先進入zookeeper的bin目錄下。 zookeeper服務端命令: 啟動命令:sh zkServer.sh start 停止命令:sh zkServer.sh s

javaweb項目啟動自動啟動rmi服務器實例

java warn 地址 public 配置 -name ace war -o 1.我們先寫一個web項目啟動時需要運行的類RmiRegisterServlet.java package com.mx.Servlet; import javax.servlet.Serv

阿裏雲監控客戶無法啟動

無法創建 logs 錯誤 process star jvm root one local 如圖報如下錯誤 [root@004 ~]# /etc/init.d/cloudmonitor start Starting cloudmonitor... Waiting f

SCCM 客戶PXE啟動無法找到操作系統 0X80004005

雲計算 雲平臺 今天和大家分享一個SCCM PXE無法找到操作系統的故障,希望可以幫助到大家。之前我們通過五篇文章給大家介紹了SCCM2016 如何與WDS集成,實現通過網絡PXE的啟動方式向客戶端PC推送操作系統安裝包的。http://blog.51cto.com/horse87/2061619ht

mysql(一)-客戶Client相關

mysql版本 CentOS Linux release 7.4.1708 (Core) 內核 3.10.0-693.el7.x86_64 Ver 15.1 Distrib 5.5.56-MariaDB 以yum方式安裝 客戶端指令 長命令 快捷縮寫 ? (\?) Syno

Tomcat啟動自動運行某程序

指示 timertask 接口 throw time test ref 自定義 pre 項目需要和tmall實現長連接,接收tmall推送的Order消息,然後對消息進行邏輯處理。 目前寫了一個servlet,實現了permit的驗證,然後對tmall進行長連接操作,啟動後

ES操作java客戶client查詢語句,模糊查詢

    sourceType:es索引名稱 fields:輸出欄位的陣列 fields[0],指定欄位,進行模糊查詢. start_time:條件查詢的時間段.可以是String型別 "yyyy-MM-dd hh:mm:ss"; setSize(1000)

[HDFS-inotify]“IOException:客戶在讀取檔案後停止

1.我想寫下一個在建立時在特定位置讀取檔案的程式碼(使用inotify)     所以我在github中修改了基於“hdfs-inotify-example”的示例程式碼https://github.com/onefoursix/ HDFS-的inotify-示例/

JAVA工程啟動自動建立資料庫、資料表

很多時候,我們會有這樣的需求: 系統首次部署時,自動建立資料庫、表 執行單元測試時,資料庫、表維持初始化狀態方便測試。 本文對這種需求的實現做了可行性驗證。 **** 注意這邊需要配置具有建庫建表許可權的資料庫使用者名稱、密碼***** 資料庫配置檔案 jdb

Eclipse初次搭建SpringCloud客戶(二)

一:建立SpringBoot專案 選擇屬性時選擇client 修改DiscSystem4Application類  新增@EnableEurekaClient和@RestController import org.springframework.beans.facto

springcloud記錄篇3-springcloud客戶ribbon和feign

一 。客戶端介紹   在springcloud中釋出的服務一般為http服務 使用http服務客戶端即可呼叫 最底層的http協議是使用它tcp協議實現 清晰理解http協議請求響應模型可以 使用Socket來進行請求 這種方式開發成本太大,java.net包提供了 Ht

SpringCloud——客戶負載平衡器(Ribbon)

一、Ribbon簡介         Ribbon是一個客戶端負載均衡器,它可以很好地控制HTTP和TCP客戶端的行為。        Ribbon中的中心概念是指定客戶端的概念。每個負載平衡器是組合的組合的一部分,它們一起工作以根據需要聯絡遠端伺服器,並且集合具有您將其

讓樹莓派每次開機啟動自動發郵件報告時間和ip資訊

<span style="font-family: Arial, Helvetica, sans-serif; background-color: rgb(255, 255, 255);"><span style="font-size:12px;">參考了這篇文章:<

虛擬機器中的Ubuntu16.04啟動自動設定解析度1920x1080

vmware不能自動適應Ubuntu16.04的解析度,而且Ubuntu16.04的display設定中也沒有1920x1080的解析度,因此需要通過修改/etc/profile檔案檔案來實現登入時自動設定解析度為1920x1080。 具體步驟如下: Ctrl+Alt+T

springWeb專案啟動自動載入方法及web專案啟動不能獲得spring的bean的解決方式

方式一:利用註解的方式和構造方法 @Service("testService") public class TestService { @Autowired private Service service; /** * spring在初始化bea

emacs啟動自動安裝package

簡介 本文主要介紹如何在emacs中,自動安裝/更新package init.el中配置追加 (require 'package) (setq package-archives '(("gnu" . "https://elpa.gnu.org/packages/")