大佬教程收集整理的这篇文章主要介绍了Spring Boot 中 Tomcat 是怎么启动的，大佬教程大佬觉得挺不错的，现在分享给大家，也给大家做个参考。
Spring Boot一个非常突出的优点就是不需要我们额外再部署Servlet容器，它内置了多种容器的支持。我们可以通过配置来指定我们需要的容器。
本文以我们平时最常使用的容器tomcat为列来介绍以下两个知识点:
对于看源代码，每个人都有自己的方法。我自己在看源代码的时候喜欢结合IDEA的Debug功能一起看。比如说现在我们要研究Spring Boot是在哪个环节点启动tomcat的，
我的思路是：tomcat在启动时会调用各个组件的init方法和start方法，那么我只需要在这些方法上打上端点，然后就能在调用栈上看出Spring Boot是在哪个环节点启用
tomcat的了。
按照这个思路，我在tomcat的Connector组件的init方法上打了端点，通过调用栈能很清楚的看出Spring Boot是在容器的onrefresh方法中调用tomcat的。
protected void onrefresh() {
super.onrefresh();
try {
this.createWebServer();
} catch (Throwable var2) {
throw new ApplicationContextException("Unable to start web server",var2);
}
}
找到了调用点，那么一切都好办了。从上面的方法中可以看出，重点内容就在this.createWebServer()这个方法中。
在Spring Boot中使用的容器类是ServletWebServerApplicationContext系列的容器，这个系列的容器可以内嵌Web容器。这个我们
可以从这个容器的属性和方法中可以看出来。
public class ServletWebServerApplicationContext extends GenericWebApplicationContext implements ConfigurableWebServerApplicationContext {
//...省略部分代码
public static final String disPATCHER_SERVLEt_name = "dispatcherServlet";
//内嵌容器
private volatile WebServer webServer;
private ServletConfig servletConfig;
//...省略部分代码
//创建Web容器
private void createWebServer() {
WebServer webServer = this.webServer;
ServletContext servletContext = this.getServletContext();
//webServer和servletContext都是null，表示还没创建容器，进入创建容器的逻辑
if (webServer == null && servletContext == null) {
//获取创建容器的工厂，可以通过WebServerFactoryCustomizer接口对这个工厂进行自定义设置
ServletWebServerFactory factory = this.getWebServerFactory();
//具体的创建容器的方法，我们进去具体看下
this.webServer = factory.getWebServer(new ServletContexTinitializer[]{this.getSelfInitializer()});
} else if (servletContext != null) {
try {
this.getSelfInitializer().onStartup(servletContext);
} catch (servletexception var4) {
throw new ApplicationContextException("CAnnot initialize servlet context",var4);
}
}
this.initPropertysources();
}
}
下面是tomcatServletWebServerFactory的getWebServer方法。
public class tomcatServletWebServerFactory的getWebServer{
//...
@Override
public WebServer getWebServer(ServletContexTinitializer... initializers) {
//创建tomcat容器
tomcat tomcat = new tomcat();
File baseDir = (this.baseDirectory != null ? this.baseDirectory
: createTempDir("tomcat"));
tomcat.setBaseDir(baseDir.getAbsolutePath());
//创建连接器，默认NIO模式，可以通过WebServerFactoryCustomizer改变具体模式
Connector connector = new Connector(this.protocol);
tomcat.getservice().addConnector(connector);
//自定义连接器
customizeConnector(connector);
tomcat.setConnector(connector);
tomcat.getHost().setAutoDeploy(false);
configureENGIne(tomcat.getENGIne());
//可以通过WebServerFactoryCustomizer添加额外的连接器，这边将这些连接器绑定到tomcat
for (Connector additionalConnector : this.additionaltomcatConnectors) {
tomcat.getservice().addConnector(additionalConnector);
}
//组测Listener、Filter和Servlet，自定义Context等操作
//这个方法可以重点看下
prepareContext(tomcat.getHost(),initializers);
//创建tomcatWebServer，并调用start方法
return gettomcatWebServer(tomcat);
}
//内嵌的tomcat容器
public tomcatWebServer(tomcat tomcat,Boolean autoStart) {
Assert.notNull(tomcat,"tomcat Server must not be null");
this.tomcat = tomcat;
this.autoStart = autoStart;
//这边触发tomcat的启动流程，是tomcat启动的入口点
initialize();
}
//...省略部分代码
}
至此Spring Boot内嵌的tomcat已将顺序启动了。那么Spring Boot是在什么时候注册dispatchServlet的呢？
Spring Boot配置Listener、Filter和Servlet可以參考我之前写的文章Spring Boot使用嵌入式容器，那怎么配置自定义Filter呢
推荐使用ServletListenerRegistrationBean、FilterRegistrationBean和ServletRegistrationBean的方式注册Listener、Filter和Servlet。
在传统的Spring MVC项目中，我们都会在web.xml中注册dispatcherServlet这个入口类，那么在Spring Boot中是在哪里注册的呢？
大家如果看Spring Boot的源代码，这边有个小技巧大家可以参考下。就是Spring Boot把之前传统项目中的配置项都通过AutoConfig的形式
做配置了。所以这边在寻找dispatcherServlet是在哪里配置的也可以顺着这个思路去寻找。
在IDEA的类查找功能中输入dispatcherServlet关键字，我们能看到一个dispatcherServletAutoConfiguration类。从名字上就能看出这个
类是dispatcherServlet的自动配置类，我们点进去看下是否是在这个类内部注册的dispatcherServlet？
@AutoConfigureOrder(ordered.HIGHEST_PRECEDENCE)
@Configuration
@ConditionalOnWebApplication(type = Type.SERVLET)
@ConditionalOnClass(dispatcherServlet.class)
@AutoConfigureAfter(ServletWebServerFactoryAutoConfiguration.class)
@EnableConfigurationProperties(ServerProperties.class)
public class dispatcherServletAutoConfiguration {
/*
* The bean name for a dispatcherServlet that will be mapped to the root URL "/"
*/
public static final String DEFAULT_disPATCHER_SERVLET_BEAN_NAME = "dispatcherServlet";
/*
* The bean name for a ServletRegistrationBean for the dispatcherServlet "/"
*/
public static final String DEFAULT_disPATCHER_SERVLET_REGISTRATION_BEAN_NAME = "dispatcherServletRegistration";
@Configuration
@Conditional(DefaultdispatcherServletCondition.class)
@ConditionalOnClass(ServletRegistration.class)
@EnableConfigurationProperties(WebMvcProperties.class)
protected static class dispatcherServletConfiguration {
private final WebMvcProperties webMvcProperties;
public dispatcherServletConfiguration(WebMvcProperties webMvcProperties) {
this.webMvcProperties = webMvcProperties;
}
@Bean(name = DEFAULT_disPATCHER_SERVLET_BEAN_Name)
public dispatcherServlet dispatcherServlet() {
dispatcherServlet dispatcherServlet = new dispatcherServlet();
dispatcherServlet.setdispatchOptionsrequest(
this.webMvcProperties.isdispatchOptionsrequest());
dispatcherServlet.setdispatchTracerequest(
this.webMvcProperties.isdispatchTracerequest());
dispatcherServlet.setThrowExceptionIfNoHandlerFound(
this.webMvcProperties.isThrowExceptionIfNoHandlerFound());
return dispatcherServlet;
}
@Bean
@ConditionalOnBean(MultipartResolver.class)
@ConditionalOnMissingBean(name = dispatcherServlet.MULTIPART_RESOLVER_BEAN_Name)
public MultipartResolver multipartResolver(MultipartResolver resolver) {
// Detect if the user has created a MultipartResolver but named it incorrectly
return resolver;
}
}
@Configuration
@Conditional(dispatcherServletRegistrationCondition.class)
@ConditionalOnClass(ServletRegistration.class)
@EnableConfigurationProperties(WebMvcProperties.class)
@Import(dispatcherServletConfiguration.class)
protected static class dispatcherServletRegistrationConfiguration {
private final ServerProperties serverProperties;
private final WebMvcProperties webMvcProperties;
private final MultipartConfigElement multipartConfig;
public dispatcherServletRegistrationConfiguration(
ServerProperties serverProperties,WebMvcProperties webMvcProperties,ObjectProvider<MultipartConfigElement> multipartConfigProvider) {
this.serverProperties = serverProperties;
this.webMvcProperties = webMvcProperties;
this.multipartConfig = multipartConfigProvider.getIfAvailable();
}
//很熟悉的代码有没有，ServletRegistrationBean就是我们上一节中介绍的注册Servlet的方式
//只不过这边注册的是dispatcherServlet这个特殊的Servlet
@Bean(name = DEFAULT_disPATCHER_SERVLET_REGISTRATION_BEAN_Name)
@ConditionalOnBean(value = dispatcherServlet.class,name = DEFAULT_disPATCHER_SERVLET_BEAN_Name)
public ServletRegistrationBean<dispatcherServlet> dispatcherServletRegistration(
dispatcherServlet dispatcherServlet) {
ServletRegistrationBean<dispatcherServlet> registration = new ServletRegistrationBean<>(
dispatcherServlet,this.serverProperties.getServlet().getServletMapping());
registration.setName(DEFAULT_disPATCHER_SERVLET_BEAN_Name);
registration.setLoadOnStartup(
this.webMvcProperties.getServlet().getLoadOnStartup());
if (this.multipartConfig != null) {
registration.setMultipartConfig(this.multipartConfig);
}
return registration;
}
}
//...省略部分代码
}
好了通过这边的介绍，我们直到dispatcherServlet是通过dispatcherServletAutoConfiguration这个自动配置类注册的。
server.tomcat.accept-count |
100.0 |
@H_269_80@maximum queue length for incoming connection requests when all possible request processing threads are in use.（BACklog的长度）
|
|---|---|---|
server.tomcat.accesslog.buffered |
true |
Whether to buffer output such that it is flushed only perioDically. |
server.tomcat.accesslog.check-exists |
false |
Whether to check for log file existence so it can be recreated it if an external process has renamed it. |
server.tomcat.accesslog.condition-if |
Whether logging of the request will only be enabled if "Servletrequest.getAttribute(conditionIf)" does not yield null. | |
server.tomcat.accesslog.condition-unless |
Whether logging of the request will only be enabled if "Servletrequest.getAttribute(conditionUnless)" yield null. | |
server.tomcat.accesslog.directory |
logs |
Directory in which log files are created. Can be absolute or relative to the tomcat base dir. |
server.tomcat.accesslog.enabled |
false |
Enable access log. |
server.tomcat.accesslog.encoding |
Character set used by the log file. Default to the system default character set. | |
server.tomcat.accesslog.file-date-format |
.yyyy-MM-dd |
Date format to place in the log file name. |
server.tomcat.accesslog.ipv6-canonical |
false |
Whether to use IPv6 canonical representation format as defined by RFC 5952. |
server.tomcat.accesslog.locale |
Locale used to format timestamps in log entries and in log file name suffix. Default to the default locale of the Java process. | |
server.tomcat.accesslog.max-days |
-1.0 |
number of days to retain the access log files before they are removed. |
server.tomcat.accesslog.pattern |
common |
Format pattern for access logs. |
server.tomcat.accesslog.prefix |
access_log |
Log file name prefix. |
server.tomcat.accesslog.rename-on-rotate |
false |
Whether to defer inclusion of the date stamp in the file name until rotate time. |
server.tomcat.accesslog.request-attributes-enabled |
false |
Set request attributes for the IP address,Hostname,protocol,and port used for the request. |
server.tomcat.accesslog.rotate |
true |
Whether to enable access log rotation. |
server.tomcat.accesslog.suffix |
.log |
Log file name suffix. |
server.tomcat.additional-tld-skip-patterns |
Comma-separated list of additional patterns that match jars to ignore for TLD scAnning. The special '?' and '*' characters can be used in the pattern to match one and only one character and zero or more characters respectively. | |
server.tomcat.BACkground-processor-delay |
10s |
Delay between the invocation of BACkgroundProcess methods. If a duration suffix is not specified,seconds will be used. |
server.tomcat.basedir |
tomcat base directory. If not specified,a temporary directory is used. | |
server.tomcat.connection-timeout |
amount of time the connector will wait,after accepTing a connection,for the request URI line to be presented. | |
server.tomcat.max-connections |
8192.0 |
@H_888_94@maximum number of connections that the server accepts and processes at any given time. Once the limit has been reached,the operaTing system may still accept connections based on the "acceptCount" property.
|
server.tomcat.max-HTTP-FORM-POST-size |
2MB |
@H_888_94@maximum size of the form content in any http post request.
|
server.tomcat.max-swallow-size |
2MB |
@H_888_94@maximum amount of request body to swallow.
|
server.tomcat.mbeanregistry.enabled |
false |
Whether tomcat's MBean Registry should be enabled. |
server.tomcat.processor-cache |
200.0 |
@H_888_94@maximum number of idle processors that will be retained in the cache and reused with a subsequent request. When set to -1 the cache will be unlimited with a theoretical maximum size equal to the maximum number of connections.
|
server.tomcat.redirect-context-root |
true |
Whether requests to the context root should be redirected by appending a / to the path. |
server.tomcat.relaxed-path-chars |
Comma-separated list of additional unencoded characters that should be allowed in URI paths. Only "< > [ \ ] ^ ` { | }" are allowed. | |
server.tomcat.relaxed-query-chars |
Comma-separated list of additional unencoded characters that should be allowed in URI query Strings. Only "< > [ \ ] ^ ` { | }" are allowed. | |
server.tomcat.remoteip.host-header |
X-ForWARDed-Host |
Name of the http header from which the remote host is extracted. |
server.tomcat.remoteip.internal-proxies |
Regular expression that matches proxies that are to be trusted. | |
server.tomcat.remoteip.port-header |
X-ForWARDed-Port |
Name of the http header used to override the original port value. |
server.tomcat.remoteip.protocol-header |
Header that holds the incoming protocol,usually named "X-ForWARDed-Proto". | |
server.tomcat.remoteip.protocol-header-https-value |
https |
Value of the protocol header inDicaTing whether the incoming request uses SSl. |
server.tomcat.remoteip.remote-ip-header |
Name of the http header from which the remote IP is extracted. For instance,X-FORWARDED-FOR. |
|
server.tomcat.resource.allow-caching |
true |
Whether static resource caching is permitted for this web application. |
server.tomcat.resource.cache-ttl |
Time-to-live of the static resource cache. | |
server.tomcat.threads.max |
200.0 |
@H_888_94@maximum amount of worker threads.
|
server.tomcat.threads.min-spare |
10.0 |
@H_888_94@minimum amount of worker threads.
|
server.tomcat.uri-encoding |
UTF-8 |
Character encoding to use to decode the URI. |
server.tomcat.use-relative-redirects |
false |
Whether http 1.1 and later LOCATIOn headers generated by a call to sendRedirect will use relative or absolute redirects. |
这边给出一个配置的列子
@H_618_566@server: port: ${port:9999} tomcat: accept-count: 200 #最好进行这段配置，默认会在tmp目录下创建，Linux有时会有定时任务删除tmp目录下的内容 basedir: my-tomcat accesslog: enabled: true pattern: '%t %a "%r" %s %s (%b M) (%D ms)' max-http-post-size: 2MB max-swallow-size: 2M uri-encoding: GBK threads: max: 100 min-spare: 10
具体使用时可以参考Spring Boo官网关于tomcat的配置。
Spring Boot还提供了很多自定义类，让用户对tomcat的组件做自定义配置。这个符合Spring的设计哲学：只提供选择，而不是强制用户使用某项技术。
关于tomcat的自定义配置类还有以下几个，大家可以按需使用。
以上是大佬教程为你收集整理的Spring Boot 中 Tomcat 是怎么启动的全部内容，希望文章能够帮你解决Spring Boot 中 Tomcat 是怎么启动的所遇到的程序开发问题。
如果觉得大佬教程网站内容还不错，欢迎将大佬教程推荐给程序员好友。
本图文内容来源于网友网络收集整理提供，作为学习参考使用，版权属于原作者。
如您有任何意见或建议可联系处理。小编QQ：384754419，请注明来意。