ManagerServlet after processing of /deploy command only check for the existence of context, but if you deploy a misconfigured application, for example with errors in web.xml or context.xml, the context is created and ManagerServlet returns OK, but the deploy is not succesfull because the application contains errors and cannot be started. Here i submit a small patch to ManagerServlet to have it check Context.getConfigured() before returning OK.
Created attachment 13799 [details] ManagerServlet patch I didn't exaustively tested it, but for the most common cases it looks to be working. I hope it won't have collateral effects i don foresee, but for sure you know it.
I forgot to mention that this patch should solve also the problem that cause the message "Cannot find message associated with key managerServlet.deployFailed" that pops out when ManagerServlet finds an error during deploy command processing. (only for English, i don't know how to translate the message in Spanish, German, Japanese etc.)
This seems like a solution (maybe incomplete though). It could be better to check other things.
I have applied your patch, thanks.