blocks|key|1225989|text|检查Tomcat创建的localhost_yyyy_mm_dd.log或localhost.yyyy-mm-dd.log日志，这些日志通常存储该类型的信息。我不期望完整的堆栈跟踪会被转储到标准输出。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1225990|entityMap^0|B|O|10|O|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Check the <code>localhost_yyyy_mm_dd.log</code> OR <code>localhost.yyyy-mm-dd.log</code> logs that Tomcat creates, these typically store that type of info. I wouldn't expect the full stacktrace to be dumped to standard out.

blocks|key|1226028|text|在WEB-INF/classes中创建一个名为logging.properties的文件，内容如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1226029|org.apache.catalina.core.ContainerBase.[Catalina].level+=+INFO
org.apache.catalina.core.ContainerBase.[Catalina].handlers+=+java.util.logging.ConsoleHandler|code-block|syntax|javascript|1226030|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

create a file named logging.properties in WEB-INF/classes with following content:

<pre><code>org.apache.catalina.core.ContainerBase.[Catalina].level = INFO
org.apache.catalina.core.ContainerBase.[Catalina].handlers = java.util.logging.ConsoleHandler
</code></pre>

blocks|key|1226070|text|也许您的应用程序是使用与Tomcat不同的JRE编译的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1226071|在您的服务器上检查java+-version，然后使用相同的版本编译代码。我出现这个错误是因为我的Eclipse标准JRE是1.6，而Tomcat使用的是1.5+--这是不能工作的。|offset|length|style|CODE|1226072|entityMap^0|0|9|D|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Maybe your application is compiled with a different JRE than Tomcat.

Check <code>java -version</code> on your server and then compile your code with the same version.
I had the error because my Eclipse standard JRE was 1.6 and Tomcat used 1.5 - this can't work.

blocks|key|1226145|text|Tomcat确实会记录堆栈跟踪，但当tomcat从IDE启动时，并不总是清楚日志文件的位置。当我从IntelliJ启动它时，CATALINA_BASE被设置为${home}/.IntelliJIdea10/system/tomcat/Unnamed_r6-idea，日志文件在[CATALINA_BASE]/logs中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1226146|要查看日志，请找到日志文件，或者编辑[CATALINA_HOME]/conf/logging.properties以将tomcat记录器输出定向到控制台。下面我在默认的tomcat配置中添加了第二个处理程序：|1226147|+org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level+=+INFO
+org.apache.catalina.core.ContainerBase.[Catalina].[localhost].handlers+=+2localhost.org.apache.juli.FileHandler,+java.util.logging.ConsoleHandler|code-block|syntax|javascript|1226148|现在，完整的堆栈跟踪出现在IntelliJ输出中：|1226149|+Dec+27,+2011+12:02:45+PM+org.apache.catalina.core.StandardContext+filterStart
+SEVERE:+Exception+starting+filter+filterChainProxy
+org.springframework.beans.factory.NoSuchBeanDefinitionException:+No+bean+named+'filterChainProxy'+is+defined+++at
+org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:529)
+.+.+.|1226150|entityMap^0|1Q|D|27|1H|3U|K|0|I|13|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|13|8|@]|D|@]|E|$]]|$1|O|3|P|5|J|7|14|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|R|$]]

Tomcat does log the stacktrace, but it is not always clear where the log files are, when tomcat is started from an IDE. When I start it from IntelliJ, <code>CATALINA_BASE</code> is set to <code>${home}/.IntelliJIdea10/system/tomcat/Unnamed_r6-idea</code>, and the log files are in in <code>[CATALINA_BASE]/logs</code>.

To see the logs, either locate the log files, or edit <code>[CATALINA_HOME]/conf/logging.properties</code> to direct tomcat logger output to console. Below I added a second handler to the default tomcat configuration:

<pre><code> org.apache.catalina.core.ContainerBase.[Catalina].[localhost].level = INFO
 org.apache.catalina.core.ContainerBase.[Catalina].[localhost].handlers = 2localhost.org.apache.juli.FileHandler, java.util.logging.ConsoleHandler
</code></pre>

Now the full stacktrace appears in the IntelliJ output:

<pre><code> Dec 27, 2011 12:02:45 PM org.apache.catalina.core.StandardContext filterStart
 SEVERE: Exception starting filter filterChainProxy
 org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'filterChainProxy' is defined at
 org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:529)
 . . .
</code></pre>

blocks|key|1226210|text|在花了最后一个小时解决几乎相同的问题后，我只想贡献自己的力量。我的解决方案是，不知何故，我们的应用程序.jar被损坏了，所以将jar放在我们的开发服务器上提供了修复。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1226211|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Just wanted to contribute after spending the last hour on a nearly identical problem. My solution was that somehow our applicatons .jar was corrupted, so placing the jar from our dev server provided a fix.

blocks|key|1011729|text|我也遇到过类似的问题。雷纳托的建议对我很有效。我使用了一个旧版本的java类文件(在WEB-INF/classes文件夹下)，这个问题就消失了。所以，应该是编译器版本不匹配。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1011730|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had a similar issue. Renato's tip worked for me. I used a older version of java class files (under WEB-INF/classes folder) and the problem disappeared. So, it should have been the compiler version mismatch.

blocks|key|1226318|text|在CentOS+6和Solr+4.4.0中|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1226319|我不得不压缩一些lib文件来解决这个错误。|1226320|cp+~/solr-4.4.0/example/lib/ext/*+/usr/share/tomcat6/lib/|code-block|syntax|javascript|1226321|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In CentOS 6 and Solr 4.4.0

I had to comp some lib files to get this error addressed

<pre><code>cp ~/solr-4.4.0/example/lib/ext/* /usr/share/tomcat6/lib/
</code></pre>

blocks|key|1226390|text|这对我来说很有用:只需删除所有的库，然后编译并运行。它会提示他们在你的项目中确认错误。在应用库之后重新运行项目。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1226391|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This did the trick for me:Just remove all the libraries and then compile and run. It would prompt their are errors in your project confirm. Rerun the project after applying the libraries.

blocks|key|1226558|text|我也遇到了同样的错误，并且在解决这个问题时费了很大的劲。花了一点时间在谷歌上搜索，找到了下面的解决方案，我的问题就解决了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1226559|该问题是由于部署路径中缺少Struts2库造成的。大多数人可能会将库放在编译时，而往往忘记附加运行时所需的库。因此，我在web部署程序集中添加了相同的库，问题就解决了。|1226560|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I too got the same error and struggled a lot in fixing this issue. Spent quiet a bit time in searching Google and found the following solution and my issue got resolved.

the issue was due to, missing Struts2 Libraries in the deployment path. Most of the folks may put the libraries for compilation and tend to forget to attach required libraries for run-time. So I added the same libraries in the web deployment assembly, and the issue was OFF.

blocks|key|1012031|text|通常，服务器JDK版本将低于部署的应用程序(使用更高的jdk版本构建)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1012032|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Generally Server JDK version will be lower than the deployed application (built with higher jdk version)

blocks|key|1226707|text|我遇到了同样的问题，一旦应用程序部署到tomcat中，它就无法启动。但是，一旦我将Struts的jars集复制到CATALINA_HOME\lib+(Tomcat+dir)目录中，它就会被解析。您不需要在WEB_INF\lib中包含这些jars，但需要在构建路径中包含它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1226708|commons-fileupload-1.2.1.jar|1226709|commons-io-1.3.2.jar|1226710|freemarker-2.3.16.jar|1226711|javassist-3.11.0.GA.jar|1226712|struts2-convention-plugin-2.2.1.jar|1226713|struts2-core-2.2.1.jar|1226714|xwork-core-2.2.1.jar|1226715|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|Y|8|@]|9|@]|A|$]]|$1|P|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|Q|$]]

I got the same issue, unable to start the application once it is deployed in tomcat. But, once I copy the Struts set of jars into CATALINA_HOME\lib (Tomcat dir) directory it is resolved. You don't need to have these jars in your WEB_INF\lib but you need to have them in your Build Path. 

commons-fileupload-1.2.1.jar

commons-io-1.3.2.jar

freemarker-2.3.16.jar

javassist-3.11.0.GA.jar

struts2-convention-plugin-2.2.1.jar

struts2-core-2.2.1.jar

xwork-core-2.2.1.jar

blocks|key|1226758|text|运行以下命令以显示终端上的catalina日志|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1226759|sh+start-camunda.sh;+tail+-f+server/apache-tomcat-8.0.24/logs/catalina.out|code-block|syntax|javascript|1226760|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Run Following command to show catalina logs on the terminal---

<pre><code>sh start-camunda.sh; tail -f server/apache-tomcat-8.0.24/logs/catalina.out
</code></pre>

When I start Tomcat I get the following error:

<pre><code>Jun 10, 2010 5:17:25 PM org.apache.catalina.core.StandardContext start
SEVERE: Error filterStart
Jun 10, 2010 5:17:25 PM org.apache.catalina.core.StandardContext start
SEVERE: Context [/mywebapplication] startup failed due to previous errors
</code></pre>

It seems odd that the logs for Tomcat would not include a stack trace. Does somebody have a suggestion for how to increase the logging in Tomcat to get stack traces for errors like this?

Tomcat startup logs - SEVERE: Error filterStart how to get a stack trace?

日志文件

服务器

编译器

Eclipse

CentOS

当我启动Tomcat时，我得到以下错误：Jun 10, 2010 5:17:25 PM org.apache.catalina.core.StandardContext startSEVERE: Error filterStartJun 10, 2010 5:17:25 PM org.apache.catalina.c...

问Tomcat启动日志-严重:错误filterStart如何获取堆栈跟踪？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Tomcat启动日志-严重:错误filterStart如何获取堆栈跟踪？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Tomcat启动日志-严重:错误filterStart如何获取堆栈跟踪？
EN