These are chat archives for spring-cloud/spring-cloud
Hi, I don't know if it is a bug or it is by design but I see unexpected
Tomcat initialized with port(s): 0 (http) entries in the start up log files from all of the instances that are deployed to yarn cluster with having the deployment property set as
2018-01-29 17:32:02.618 INFO 24043 --- [ main] s.b.c.e.t.TomcatEmbeddedServletContainer : Tomcat initialized with port(s): 0 (http) 2018-01-29 17:32:02.631 INFO 24043 --- [ main] o.apache.catalina.core.StandardService : Starting service Tomcat 2018-01-29 17:32:02.632 INFO 24043 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet Engine: Apache Tomcat/8.5.11 2018-01-29 17:32:02.882 INFO 24043 --- [ost-startStop-1] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext 2018-01-29 17:32:02.882 INFO 24043 --- [ost-startStop-1] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 6107 ms
All of the instance launched in a Yarn cluster will be therefore identified as
hostname.domain:0 when registering themselves to Eureka server. This causes registry record to be overwritten.
Why does Tomcat get initialized with port 0? Is there any workaround to address this issue so each one of them will launch its embedded tomcat with none 0 port?
ConfigurationClassPostProcessororder of execution as would it possible to execute custom
ConfigurationClassPostProcessorby setting higher precedence?
BeanDefinitionRegistryPostProcessoris always executed before a
BeanPostProcessor, so you don't have to do anything special, if I understand the question.