404 errors with JSP page (complex) but NO errors for simple jsp page

Question

Hey Folks,

Extremely frustrated right now. I can't seem to get my Web App to run and continuously get 404 errors for the index.jsp page. I created a test web app and copied over just the index.jsp page to just that test web app and it runs fine without any tuning. But when I deploy the web app to the same App Service WITHOUT any changes to the App Service or the index.jsp page, I get 404 errors.

I deploy using the plugin recommended by Azure for Eclipse and, again, deployment of the 'test' index.jsp works fine but the deployment of the full page comes back with a 404 error when trying to access the index.jsp . Extremely weird and frustrating.

FYI, the Web App works fine in my local Tomcat instance. I just can't even get to the point that I can test the web app in the Azure App Service environment. I know I'm going to have to make changes to the Web App simply because of things like DB credential changes but I'm not even getting to the initial index.jsp to get started.

Also, note that I'm using the initial Free service to test out Azure before I spend any money on it. Note sure if there are limits to getting it running.

Any assistance would be greatly appreciated ...

Neil

Answer 1

Neil, we apologize for the frustration that you have encountered.

If you hit any resource quotas on your free tier app service, it should in most cases result in 503 errors, which means your site is stopped and will resume once the resource quota timer resets. If you have not hit any 503 errors, you are likely not encountering any resource quota issues.

The only times I have encountered a 404 error with Eclipse deployed apps were when the customer forgot to transfer the server.xml data sources to context.xml as the default Tomcat server.xml cannot be edited but you're using JSP.

One final item to check would be the diagnose and solve blade of your web app. This is the same powerful tool that our support engineers use to troubleshoot issues. To learn more about it, read about it here. This might help to uncover any issues.

If you have not located the issue and the diagnose and solve blade does not work, please reach out to us at azcommunity@microsoft.com with the subject ATTN: Bryan and in the body of the email include your Azure Subscription ID.

If you have resolve the issue already, we would appreciate it if you shared the solution for the community. We look forward to your reply.