Bug 56442 - ClassNotFoundException does not produce error
Summary: ClassNotFoundException does not produce error
Status: RESOLVED WORKSFORME
Alias: None
Product: Tomcat 8
Classification: Unclassified
Component: WebSocket (show other bugs)
Version: 8.0.5
Hardware: PC Linux
: P2 minor (vote)
Target Milestone: ----
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-22 12:50 UTC by Thom H
Modified: 2014-04-22 15:41 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thom H 2014-04-22 12:50:50 UTC
I was attempting to deploy my war file with an endpoint annotation defined in it to my tomcat server. When I deployed it, I received no error messages, but the endpoint was returning 404.

I switched to tomcat 7.0.52 and dropped the war file in there. I received a stack trace because one of the dependent classes was not included in the war file. Once I fixed the classptath problems, the error disappeared and the endpoint showed up. I moved this back to tomcat 8.0.5 and it is now working fine.

The problem is that the error does not show up in the log. An error on the dependent class needs to show up in the log to tell the deployer there is a problem with the endpoint instead of silently not standing it up.

This problem can be re-created by creating a basic endpoint with one dependent class not in the class path.
Comment 1 Mark Thomas 2014-04-22 15:41:30 UTC
The CNFE is already logged with a clean install of 8.0.x.