You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tomcat.apache.org by Adam Štulpa <st...@gmail.com> on 2012/05/15 11:22:47 UTC

Tomcat returns 404 on wrong deployed applications

*Hi,*
*

we have several REST applications using Spring MVC. Sometimes some of these
applications after deploy don’t start (because of error in spring
context,...). Application is deployed but it isn’t running. Our javascript
client access resource url. It gets 404 status, therefore it assumes, that
resource doesn’t exist. So we are unable to detect this error. More
appropriate for us would be http status 500. Is possible change this
default tomcat behavior? For example Jetty returns 503 on such error.*
*
*
*Regards,*
*Adam*
*
*