That status check page actually queries the server to see if any workflow has changed recently. To do that it has to get a working connection from the midtier to a (possibly load balanced) AR Server and from the AR Server to the (possibly load balanced) database and back. You can see all the logs move if you are watching them SQL log(s).
One thing… you have to check for the TEXT “200_OK” in the body of the status check web page, not the HTML return code of 200. When the web page comes back it will always be 200 (otherwise you wouldn’t get a web page). The HTML return code of 200 just tells you that the web server is working. Doug > On Jul 12, 2016, at 4:48 PM, LJ LongWing <[email protected]> wrote: > > ** > As I understand it, the StatusCheck.jsp makes a few servlet calls to check > for various things. Typically, the server is up, and the Status Check > reports it as up. I have had scenarios where the application server was > entirely off, and was the only app server on the Mid-Tier server, and the > Status Check was reporting as 200_OK....I've also experienced where it was > NOT reporting 200_OK when the server was in fact online. I never went into > specifics of why it was reporting the wrong status...I had my own servlet > that I used that gave me everything I needed, accurately, without fail, so I > simply used it instead. I was using Remedy/Mid-Tier 8.1.02 when this > inconsistency was happening. > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
