Skip navigation

Recover from HTTP 404 Error when arserver becomes available

score 40
You have not voted. Not Planned

When ARServer is not (yet) available when DWP/Smart IT is started the users will get an empty page after startup. A client log will show a 404 error, which is not logged on the server side. Even if arserver is available again, and the arsystem is accessible again using the Mid Tier, DWP/Smart IT will still serve a 404 error to it's users. As a workaround the DWP/Smart IT server can be restarted.

 

Unfortunately and although the Remedy Mid tier does recover under these conditions, this behavior is considered as expected by the BMC Product Engineering team and I need to launch an idea to get it fixed. So, please vote this idea up.

 

Test result:

  1. Stop arserver
  2. Stop Smart IT/MyIT application
  3. Start Smart IT/MyIT application
  4. Wait until the application is fully started
  5. When trying to access /ux/myitapp the server returns 404
  6. Start  arserver
  7. Wait until arserver is fully started
  8. When trying to access /ux/myitapp the server returns 404
  9. Waited several hours
  10. When trying to access /ux/myitapp the server returns 404

 

Expected result: same behavior as BMC Mid Tier

  1. Stop arserver
  2. Stop Smart IT/MyIT application
  3. Start Smart IT/MyIT application
  4. Wait until the application is fully started
  5. When trying to access /ux/myitapp the server returns an error message telling arserver is not reachable
  6. Start  arserver
  7. Wait until arserver is fully started
  8. When trying to access /ux/myitapp the server shows the login page and functions correctly

Comments

Vote history