SpringBoot应用程序启动多次并从logstash断开连接

我有一个在docker上运行的springboot应用程序（Spring Boot v1.3.5.RELEASE），它使用./mvnw;SpringBoot应用程序启动多次并从logstash断开连接

它“重新启动” 1-2分钟后，和第二开始后他们不发送任何日志logstash ..

在第一次启动，我们看到下面的日志之后的第二

2016-07-27 08:54:29,616 DEBUG [background-preinit] logging: Logging Provider: org.jboss.logging.Slf4jLoggerProvider found via system property

错误一个记录提供商日志缺少..

**2016-07-27 08:54:25,386 INFO [restartedMain] DemoApp: Starting DemoApp on 7adf92b8bc96 with PID 85 (/home/infoowl/project/target/classes started by infoowl in /home/infoowl/project)** 
    2016-07-27 08:54:25,471 DEBUG [restartedMain] DemoApp: Running with Spring Boot v1.3.5.RELEASE, Spring v4.2.6.RELEASE 
    2016-07-27 08:54:25,487 INFO [restartedMain] DemoApp: The following profiles are active: dev 
    2016-07-27 08:54:29,616 DEBUG [background-preinit] logging: Logging Provider: org.jboss.logging.Slf4jLoggerProvider found via system property 
    2016-07-27 08:54:32,436 INFO [restartedMain] DemoApp: Started DemoApp in 9.865 seconds (JVM running for 14.572) 
    2016-07-27 08:54:45,937 DEBUG [restartedMain] HttpURLConnection: [email protected] pairs: {GET /config/transformation/dev/master HTTP/1.1: null}{Accept: application/json, application/*+json}{Authorization: Basic YWRtaW46YWRtaW4=}{User-Agent: Java/1.8.0_91}{Host: registry:8761}{Connection: keep-alive} 
    2016-07-27 08:54:46,512 DEBUG [restartedMain] HttpURLConnection: [email protected] pairs: {null: HTTP/1.1 200 OK}{Server: Apache-Coyote/1.1}{X-Content-Type-Options: nosniff}{X-XSS-Protection: 1; mode=block}{Cache-Control: no-cache, no-store, max-age=0, must-revalidate}{Pragma: no-cache}{Expires: 0}{X-Application-Context: jhipster-registry:dev,native:8761}{Content-Type: application/json;charset=UTF-8}{Transfer-Encoding: chunked}{Date: Wed, 27 Jul 2016 08:54:46 GMT} 
    2016-07-27 08:54:46,777 INFO [restartedMain] DemoApp: The following profiles are active: dev 
    2016-07-27 08:55:01,347 WARN [restartedMain] ConfigurationClassPostProcessor: Cannot enhance @Configuration bean definition 'refreshScope' since its singleton instance has been created too early. The typical cause is a non-static @Bean method with a BeanDefinitionRegistryPostProcessor return type: Consider declaring such methods as 'static'. 
    2016-07-27 08:55:03,767 DEBUG [restartedMain] AsyncConfiguration: Creating Async Task Executor 
    2016-07-27 08:55:07,072 DEBUG [restartedMain] MetricsConfiguration: Registering JVM gauges 
    2016-07-27 08:55:07,169 DEBUG [restartedMain] MetricsConfiguration: Initializing Metrics JMX reporting 
    2016-07-27 08:55:07,281 INFO [restartedMain] MetricsConfiguration: Initializing Metrics Log reporting 
    2016-07-27 08:55:16,352 INFO [localhost-startStop-1] WebConfigurer: Web application configuration, using profiles: [dev] 
    2016-07-27 08:55:16,359 DEBUG [localhost-startStop-1] WebConfigurer: Initializing Metrics registries 
    2016-07-27 08:55:16,383 DEBUG [localhost-startStop-1] WebConfigurer: Registering Metrics Filter 
    2016-07-27 08:55:16,400 DEBUG [localhost-startStop-1] WebConfigurer: Registering Metrics Servlet 
    2016-07-27 08:55:16,402 INFO [localhost-startStop-1] WebConfigurer: Web application fully configured 
    2016-07-27 08:55:19,343 INFO [localhost-startStop-1] CoreApp: Running with Spring profile(s) : [dev] 
    2016-07-27 08:55:24,670 INFO [restartedMain] LoggingConfiguration: Initializing Logstash logging 
    2016-07-27 08:55:24,781 INFO [restartedMain] LoggingConfiguration: Logstash customFields: '{"app_name":"transformation","app_port":"9093","instance_id":"transformation:4afb19b3a2763ed887b8d69d246082e6"}', config: 'net.info[email protected]96d9ebe[enabled=true,host=elk-logstash,port=5000,queueSize=512]' 
    2016-07-27 08:55:35,367 DEBUG [restartedMain] CacheConfiguration: No cache 
    2016-07-27 08:55:40,071 DEBUG [restartedMain] DatabaseConfiguration: Configuring Mongeez 
    2016-07-27 08:55:40,245 INFO [restartedMain] FilesetXMLReader: Parsing XML Fileset file master.xml 
    2016-07-27 08:55:40,275 INFO [restartedMain] FilesetXMLReader: Num of changefiles found 0 
    2016-07-27 08:55:41,089 DEBUG [restartedMain] SwaggerConfiguration: Starting Swagger 
    2016-07-27 08:55:41,218 DEBUG [restartedMain] SwaggerConfiguration: Started Swagger in 118 ms 
    2016-07-27 08:55:55,610 WARN [restartedMain] URLConfigurationSource: No URLs will be polled as dynamic configuration sources. 
    2016-07-27 08:55:56,975 WARN [restartedMain] URLConfigurationSource: No URLs will be polled as dynamic configuration sources. 
    2016-07-27 08:56:00,036 DEBUG [cron4j::scheduler[20b6349f63f32eea2d00877b000001562b91269c7714a479]::launcher[20b6349f63f32eea238ca33a000001562b9155042b804084]] CronPlugin: Found crontab config url [email protected] 
    **2016-07-27 08:56:00,788 INFO [restartedMain] DemoApp: Starting DemoApp on 7adf92b8bc96 with PID 85 (/home/infoowl/project/target/classes started by infoowl in /home/infoowl/project)** 
    2016-07-27 08:56:00,788 DEBUG [restartedMain] DemoApp: Running with Spring Boot v1.3.5.RELEASE, Spring v4.2.6.RELEASE 
    2016-07-27 08:56:00,788 INFO [restartedMain] DemoApp: The following profiles are active: dev 
    2016-07-27 08:56:01,290 INFO [restartedMain] DemoApp: Started DemoApp in 0.899 seconds (JVM running for 103.426)

另一个观察..看到第二次创业就是“0.899秒”这是不可能的..其实这似乎第二个是不是一个真正的开始，但logstash连接不见了。

这第二次启动的原因是什么？我应该在哪里检查和调查;

来源

2016-07-28 ygk

'restartedMain'线程名称告诉我你在类路径上有Spring Boot的DevTools。重启你的应用程序可能是为了响应它正在监视的文件的更改。故意在班级路线上吗？ –

我发现了问题，细节在这里; https://github.com/spring-cloud/spring-cloud-stream/issues/605

来源

2016-08-19 18:04:22 ygk

从documentation：

使用弹簧引导devtools会自动重启应用程序只要在classpath变化的文件。

您可以exclude resources或disable restarts。

来源

2016-07-28 21:44:24 alpert

他们被禁用。我怎样才能检查devtools做重启？是否有任何特定的日志可供排除故障 – ygk

“restartedMain”线程是：https：//github.com/spring-projects/spring-boot/blob/master/spring-boot-devtools/src/main/java /org/springframework/boot/devtools/restart/RestartLauncher.java这是devtools的一部分。 – alpert

甚至重新启动被禁用莫名其妙的应用程序正在重新启动..实际上我发现，如果我在应用程序中使用“@EnableBinding”，它有这个问题。 rabbitmq整合需要这个加注..任何想法？ – ygk

SpringBoot应用程序启动多次并从logstash断开连接

回答

相关问题