In a Web-based architecture, if you try to hit the URL, it shows an error like "Page Can Not be Displayed, How to troubleshoot this issue?
Ans:
The Flow of Request happens from Load Balancer >> Webserver >> Appserver >> DB .
so the investigation for such issues should also follow the same routes.
1) Try to check if the url is responding from your end. ( this will eliminate if its specific to a user or its error for every one)
2) Check the Webserver if its running or not , If its not running start it.
3) Check if the application server and application is running .. if not start it.
4) Try to access the Aplication directly from the Appserver .. ie using the http transport port. ie wc_defalut .. ( this will identify if the error is due to App server or is with the Webserver/plugin)
5) Check for the errors in the Appserver and web server logs.
6) Check for the config in the plugin file to ensure that the url which is being hit is avaliable in the plugin-xml.cfg ( If it is not then it could be possible that the plugin was not regeneraed and propagated after the deployment)
7) Enable the trace in the plugin-xml.cfg to understand in the plugin logs whether the plugin is forwarding the req to the appservers or not .
8) Lastly also check if the page which you are requesting is avaliable within the web modules.
Ans:
The Flow of Request happens from Load Balancer >> Webserver >> Appserver >> DB .
so the investigation for such issues should also follow the same routes.
1) Try to check if the url is responding from your end. ( this will eliminate if its specific to a user or its error for every one)
2) Check the Webserver if its running or not , If its not running start it.
3) Check if the application server and application is running .. if not start it.
4) Try to access the Aplication directly from the Appserver .. ie using the http transport port. ie wc_defalut .. ( this will identify if the error is due to App server or is with the Webserver/plugin)
5) Check for the errors in the Appserver and web server logs.
6) Check for the config in the plugin file to ensure that the url which is being hit is avaliable in the plugin-xml.cfg ( If it is not then it could be possible that the plugin was not regeneraed and propagated after the deployment)
7) Enable the trace in the plugin-xml.cfg to understand in the plugin logs whether the plugin is forwarding the req to the appservers or not .
8) Lastly also check if the page which you are requesting is avaliable within the web modules.
No comments:
Post a Comment