Warning: file_get_contents(/data/phpspider/zhask/data//catemap/9/java/386.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Java 尝试使用STS以调试模式启动时,Tomcat超时_Java_Eclipse_Tomcat - Fatal编程技术网

Java 尝试使用STS以调试模式启动时,Tomcat超时

Java 尝试使用STS以调试模式启动时,Tomcat超时,java,eclipse,tomcat,Java,Eclipse,Tomcat,从今天早上开始,我在STS中启动调试模式时一直遇到问题,但似乎无法找到导致这种行为突然改变的原因。当我在eclipse/STS中单击调试图标时,会出现以下情况 加载了一个显示“jdbcOdbcDriver.finalize()行:不可用”的选项卡 服务器在45秒后超时 控制台也给了我这个长日志,但我没有看到其中发生任何错误 Jan 22, 2015 11:04:35 AM org.apache.catalina.core.AprLifecycleListener init INFO: The A

从今天早上开始,我在STS中启动调试模式时一直遇到问题,但似乎无法找到导致这种行为突然改变的原因。当我在eclipse/STS中单击调试图标时,会出现以下情况

加载了一个显示“jdbcOdbcDriver.finalize()行:不可用”的选项卡 服务器在45秒后超时

控制台也给了我这个长日志,但我没有看到其中发生任何错误

Jan 22, 2015 11:04:35 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: C:\Program Files\Java\jre7\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Python27\;C:\Python27\Scripts;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Java\jdk1.7.0_67\bin;.
Jan 22, 2015 11:04:36 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server:clearbox' did not find a matching property.
Jan 22, 2015 11:04:36 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Jan 22, 2015 11:04:36 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8443"]
Jan 22, 2015 11:04:36 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Jan 22, 2015 11:04:36 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1753 ms
Jan 22, 2015 11:04:36 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Jan 22, 2015 11:04:36 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.47
Jan 22, 2015 11:04:38 AM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(C:\Users\chris@empatico.ca\Documents\workspace-sts-3.6.1.RELEASE\.metadata\.plugins\org.eclipse.wst.server.core\tmp3\wtpwebapps\clearbox\WEB-INF\lib\tomcat-embed-core-7.0.52.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/servlet/Servlet.class
Jan 22, 2015 11:04:38 AM org.apache.catalina.loader.WebappClassLoader validateJarFile
INFO: validateJarFile(C:\Users\chris@empatico.ca\Documents\workspace-sts-3.6.1.RELEASE\.metadata\.plugins\org.eclipse.wst.server.core\tmp3\wtpwebapps\clearbox\WEB-INF\lib\tomcat-embed-el-7.0.52.jar) - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class: javax/el/Expression.class
Jan 22, 2015 11:04:46 AM org.apache.catalina.core.ApplicationContext log
INFO: No Spring WebApplicationInitializer types detected on classpath
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/C:/Users/chris@empatico.ca/Documents/workspace-sts-3.6.1.RELEASE/.metadata/.plugins/org.eclipse.wst.server.core/tmp3/wtpwebapps/clearbox/WEB-INF/lib/logback-classic-1.0.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/C:/Users/chris@empatico.ca/Documents/workspace-sts-3.6.1.RELEASE/.metadata/.plugins/org.eclipse.wst.server.core/tmp3/wtpwebapps/clearbox/WEB-INF/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.

任何人都有这样的问题,如果有,我能做些什么来解决这个看似随机的问题?

如果我理解正确,在正常模式下一切正常?有时eclipse中太多的断点会导致这种错误。我不知道真正的原因。@vincent是的,当正常启动tomcat时,它会顺利启动。它需要30秒,但除此之外工作正常。您可以增加启动超时值。如果您的服务器是在STS中定义的,您应该能够在Servers选项卡中看到它。双击-->概览窗口打开-->扩展超时部分-->将开始时间(以秒为单位)增加到更大的值,例如800。现在您已经增加了ur超时,tomcat在800秒之前不会被强制关闭,如果有任何其他错误,您可以在控制台中检查日志/exception@Arkantos尝试提高超时时间,它工作了,但返回到原来的值,ti也工作了。这几乎就像它自己痊愈了一样。试着回忆一下你在应用程序中是否做了任何更改。。我怀疑java/tomcat是自愈的;)