Since last 3-4 times we have observed, after patching/reboot.. Riskauth instances gets initialized fine but no requests gets served by it.
In earlier cases, multiple restarts lead to resolution of an issue. Today, similar issue encountered in Production but restarts not helping it out.
Release : 9.1
Component : AuthMinder(Arcot WebFort)
RiskMinder(Arcot RiskFort)
If there are multiple Risk servers behind a load balancer then we have to isolate the issue if that is related to Risk server or a Load Balancer issue and below are some of the ways it can be done.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsdl="http://ws.arcot.com/RiskFortEvaluateRiskAPI/3.0/wsdl">
<soapenv:Header/>
<soapenv:Body>
<wsdl:EvaluateRiskRequest>
<wsdl:deviceContext>
<wsdl:deviceSignature>{"VERSION": "2.1.2", "MFP": {"Browser": {"UserAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0", "Vendor": "", "VendorSubID": "", "BuildID": "20181001000000", "CookieEnabled": true}, "IEPlugins": {}, "NetscapePlugins": {}, "Screen": {"FullHeight": 1080, "AvlHeight": 1040, "FullWidth": 1920, "AvlWidth": 1920, "ColorDepth": 24, "PixelDepth": 24}, "System": {"Platform": "Win32", "OSCPU": "Windows NT 10.0; Win64; x64", "systemLanguage": "en-US", "Timezone": 180}}, "ExternalIP": "10.x.x.x", "MESC": {"mesc": "mi=2;cd=150;id=30;mesc=335538;mesc=351502"}}</wsdl:deviceSignature>
<wsdl:deviceIDs>
<wsdl:deviceIDItem>
<wsdl:deviceIDType>HTTP_COOKIE</wsdl:deviceIDType>
<wsdl:deviceIDValue>QYixg1pv7VmxPOa....................</wsdl:deviceIDValue>
</wsdl:deviceIDItem>
</wsdl:deviceIDs>
</wsdl:deviceContext>
<wsdl:locationContext>
<wsdl:clientIPAddress>10.x.x.x</wsdl:clientIPAddress>
</wsdl:locationContext>
<wsdl:userContext>
<wsdl:orgName>DEFAULTORG</wsdl:orgName>
<wsdl:userName>USER1</wsdl:userName>
</wsdl:userContext>
</wsdl:EvaluateRiskRequest>
</soapenv:Body>
</soapenv:Envelope>
Once you validate the Risk server is taking requests and processing it fine then you can engage with the Load Balancer team and ask them to look into why the requests are not flowing to that server.