java - BigIP - Tomcat 8 连接在从 tomcat 6 升级时被拒绝

Question

Tomcat 开始监听端口并且应用程序也已部署，但是当我访问 URL 时出现连接被拒绝错误。BigIP是否无法识别服务器上tomcat 8打开的端口有什么问题吗？

虽然当我恢复到 tomcat 6(启动和停止它)然后再次尝试使用 tomcat 8 时，它有时会开始接收连接，这很奇怪，我无法找到原因。可能是什么问题？

Jun 13, 2017 5:56:32 AM org.apache.tomcat.util.digester.SetPropertiesRule beginWARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Valve} Setting property 'resolveHosts' to 'false' did not find a matching property.Jun 13, 2017 5:56:32 AM org.apache.catalina.core.AprLifecycleListener lifecycleEventINFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: :/myPath/libJun 13, 2017 5:56:32 AM org.apache.coyote.AbstractProtocol initINFO: Initializing ProtocolHandler ["http-bio-9030"]Jun 13, 2017 5:56:32 AM org.apache.catalina.startup.Catalina loadINFO: Initialization processed in 854 msJun 13, 2017 5:56:32 AM org.apache.catalina.users.MemoryUserDatabase openSEVERE: The specified user database [conf/tomcat-users.xml] could not be foundJun 13, 2017 5:56:32 AM org.apache.catalina.core.StandardService startInternalINFO: Starting service CatalinaJun 13, 2017 5:56:32 AM org.apache.catalina.core.StandardEngine startInternalINFO: Starting Servlet Engine: Apache Tomcat/8.0.30Jun 13, 2017 5:56:33 AM org.apache.jasper.servlet.TldScanner scanJarsINFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.Jun 13, 2017 5:56:33 AM org.apache.catalina.startup.HostConfig deployWARINFO: Deploying web application archive /mypath/MyWar.warJun 13, 2017 5:56:43 AM org.apache.jasper.servlet.TldScanner scanJarsINFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.Jun 13, 2017 5:56:43 AM org.apache.catalina.core.ApplicationContext logINFO: No Spring WebApplicationInitializer types detected on classpathJun 13, 2017 5:56:43 AM org.apache.catalina.core.ApplicationContext logINFO: Initializing Spring root WebApplicationContextJun 13, 2017 5:57:06 AM org.apache.catalina.core.ApplicationContext logINFO: Initializing Spring FrameworkServlet 'myServlet'Jun 13, 2017 5:57:06 AM org.apache.catalina.startup.HostConfig deployWARINFO: Deployment of web application archive /mypath/MyWar.war has finished in 33,424 msJun 13, 2017 5:57:06 AM org.apache.coyote.AbstractProtocol startINFO: Starting ProtocolHandler ["http-bio-9030"]'Jun 13, 2017 5:57:06 AM org.apache.catalina.startup.Catalina startINFO: Server startup in 33845 ms

Answer 1

Each incoming request requires a thread for the duration of that request. If more simultaneous requests are received than can be handled by the currently available request processing threads, additional threads will be created up to the configured maximum (the value of the maxThreads attribute). If still more simultaneous requests are received, they are stacked up inside the server socket created by the Connector, up to the configured maximum (the value of the acceptCount attribute). Any further simultaneous requests will receive "connection refused" errors, until resources are available to process them.

更多信息请参阅 https://tomcat.apache.org/tomcat-8.0-doc/config/http.html