CODEWITHSUNDEEP
javatomcattomcat8
KyrinWoo
KyrinWoo

Reputation: 347

Tomcat-8.0.44: Why a SEVERE log "One or more Filters failed to start"

I installed Tomcat-8.0.44 and put a war file named bimserver.war in webapps folder. But when I ran the startup.bat routine, I got two Severe Log info:

24-May-2017 01:15:53.065 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more Filters failed to start. Full details will be found in the appropriate container log file
24-May-2017 01:15:53.068 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/bimserver] startup failed due to previous errors

It seems that some filters of tomcat failed to start. This prevented bimserver from starting. How should the filters be configured?

Upvotes: 13

Views: 40095

Answers (4)

Ramya Musunuru
Ramya Musunuru

Reputation: 471

Detailed logs on such exceptions can be found under CATALINA_HOME/logs/localhost.<timestamp>.log

Refer to latest timestamp log.

Sometimes, application specific logs(under tomcat logs) will also contain detailed info, depending upon application logging.

Upvotes: 2

Rao Aadil
Rao Aadil

Reputation: 11

In my case I haven't set my workspace to build automaticaly

in eclipse

enter image description here

Upvotes: 0

jgrocha
jgrocha

Reputation: 3052

Using Tomcat 8.5.30 on Ubuntu 18.04, I was getting the error:

08-Apr-2019 00:02:16.994 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more Filters failed to start. Full details will be found in the appropriate container log file

The details were in the log file: /var/lib/tomcat8/logs/localhost.2019-04-08.log (the same as /var/log/tomcat8/localhost.2019-04-08.log).

The details were:

08-Apr-2019 00:02:01.869 SEVERE [localhost-startStop-1] org.apache.catalina.core.StandardContext.filterStart Exception starting filter [CorsFilter]
 javax.servlet.ServletException: It is not allowed to configure supportsCredentials=[true] when allowedOrigins=[*]

I was trying to use * for the cors.allowed.origins with cors.support.credentials set to true. Setting cors.support.credentials to false solved the problem.

Finding and checking the correct log file solved my problem.

Upvotes: 8

Kohei TAMURA
Kohei TAMURA

Reputation: 5122

As your log suggests (Full details will be found in the appropriate container log file), you should check Tomcat log, and then you can find the message starts with Exception starting filter ....

Upvotes: 5

Related Questions