View Forum Topic

Forums
CS5220
Tomcat doesn't run.

Author	Message
smahbub2 Posts: 12	Posted 09:30 Sep 25, 2018 \| I keep getting this "tomcat failed to start" message and I don't know how to fix it. I've deleted the sever and added it again and I've looked through stack overflow but everything I tried doesn't work. It worked before I added the annotations. Does anyone else have this problem? Do you know how to fix it? Any help would be appreciated. This is the first error of the stack trace if it helps. SEVERE: A child container failed during start java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/springrest]] Attachments: Tomcat fail.png
cysun Posts: 2935	Posted 09:34 Sep 25, 2018 \| There should be more descriptive error message in the Console view. So far I've seen two students in the class having the same problem, and in both cases it was due to some corrupted dependency jar file (you should see an error message complaining something about "Zip LOC"). See this post on how to fix corrupted dependency.

Author

Message

smahbub2

Posts: 12

Posted 09:30 Sep 25, 2018 |

I keep getting this "tomcat failed to start" message and I don't know how to fix it. I've deleted the sever and added it again and I've looked through stack overflow but everything I tried doesn't work. It worked before I added the annotations.

Does anyone else have this problem? Do you know how to fix it? Any help would be appreciated.

This is the first error of the stack trace if it helps.

SEVERE: A child container failed during start java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/springrest]]

Attachments:

Tomcat fail.png

cysun

Posts: 2935

Posted 09:34 Sep 25, 2018 |

There should be more descriptive error message in the Console view.

So far I've seen two students in the class having the same problem, and in both cases it was due to some corrupted dependency jar file (you should see an error message complaining something about "Zip LOC"). See this post on how to fix corrupted dependency.