Skip to main content

Return to Answer

improved readability
Source Link
edit approved Apr 21, 2014 at 15:08
Muath
edit approved Apr 21, 2014 at 15:08
Muath
  • 4.4k
  • 12
  • 44
  • 70

This is potentially caused by conflicting jars in your webappwebapp and tomcattomcat. If If you have any tomcat or websocket specific jars that you are including in your build and that end up in the {TOMCAT_HOME}/webapps/{YOUR_WEBAPP}/WEB-INF/lib{TOMCAT_HOME}/webapps/{YOUR_WEBAPP}/WEB-INF/lib directory, they may be causing the conflict with jarsjars in the {TOMCAT_HOME}/lib directory. Keep in mind that the jars might not be named precisely the same. I experienced this exact problem before and removing the duplicate jars from the {TOMCAT_HOME}/webapps/{YOUR_WEBAPP}/WEB-INF/lib directory{TOMCAT_HOME}/webapps/{YOUR_WEBAPP}/WEB-INF/lib directory fixed the 404 error.

As a further note, if you are using gradle to compile your webapp with the 'war' plugin, there is a 'providedCompile' dependency that you can use that will put the necessary jars on your classpath for testing, importing into eclipse, etc. but will not include them in the actual built war (to specifically avoid scenarios like this)

This is potentially caused by conflicting jars in your webapp and tomcat. If you have any tomcat or websocket specific jars that you are including in your build and that end up in the {TOMCAT_HOME}/webapps/{YOUR_WEBAPP}/WEB-INF/lib directory, they may be causing the conflict with jars in the {TOMCAT_HOME}/lib directory. Keep in mind that the jars might not be named precisely the same. I experienced this exact problem before and removing the duplicate jars from the {TOMCAT_HOME}/webapps/{YOUR_WEBAPP}/WEB-INF/lib directory fixed the 404 error.

As a further note, if you are using gradle to compile your webapp with the 'war' plugin, there is a 'providedCompile' dependency that you can use that will put the necessary jars on your classpath for testing, importing into eclipse, etc. but will not include them in the actual built war (to specifically avoid scenarios like this)

This is potentially caused by conflicting jars in your webapp and tomcat. If you have any tomcat or websocket specific jars that you are including in your build and that end up in the {TOMCAT_HOME}/webapps/{YOUR_WEBAPP}/WEB-INF/lib directory, they may be causing the conflict with jars in the {TOMCAT_HOME}/lib directory. Keep in mind that the jars might not be named precisely the same. I experienced this exact problem before and removing the duplicate jars from the {TOMCAT_HOME}/webapps/{YOUR_WEBAPP}/WEB-INF/lib directory fixed the 404 error.

As a further note, if you are using gradle to compile your webapp with the 'war' plugin, there is a 'providedCompile' dependency that you can use that will put the necessary jars on your classpath for testing, importing into eclipse, etc. but will not include them in the actual built war (to specifically avoid scenarios like this)

Source Link
Justin
Justin
  • 11
  • 1

This is potentially caused by conflicting jars in your webapp and tomcat. If you have any tomcat or websocket specific jars that you are including in your build and that end up in the {TOMCAT_HOME}/webapps/{YOUR_WEBAPP}/WEB-INF/lib directory, they may be causing the conflict with jars in the {TOMCAT_HOME}/lib directory. Keep in mind that the jars might not be named precisely the same. I experienced this exact problem before and removing the duplicate jars from the {TOMCAT_HOME}/webapps/{YOUR_WEBAPP}/WEB-INF/lib directory fixed the 404 error.

As a further note, if you are using gradle to compile your webapp with the 'war' plugin, there is a 'providedCompile' dependency that you can use that will put the necessary jars on your classpath for testing, importing into eclipse, etc. but will not include them in the actual built war (to specifically avoid scenarios like this)