B - Production Support » KFH Support

Updated by Nazri

====================
Hi,

After doing some investigation on the provided log files, we found out that the PowerCard responded only after 9 minutes during the issue's occurrence.
FYI, this issue happens when user attempts to proceed from the iPay Details page to iPay Confirm page.
During this time, IB will made a request for an account inquiry from PowerCard.
Below is a related part from the nohup_f0.out log file:

07:54:22,886 INFO  [STDOUT] Begin Account Enquiry..............................

(After 9 minutes)

08:03:07,866 INFO  [STDOUT] Request Msg: <?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soapenv:Body>
<hpsService xmlns="http://hps.ws.service/">
<login xmlns="">kfhib</login>
<passwd xmlns="">kfh1234</passwd>
<functionName xmlns="">IB_ACCOUNT_INQUIRY</functionName>
<args xmlns="">
<ns1:String xmlns:ns1="http://hps.ws.service/types/">192</ns1:String>
<ns2:String xmlns:ns2="http://hps.ws.service/types/">XXXXXXXX1219</ns2:String>
<ns3:String xmlns:ns3="http://hps.ws.service/types/">XXXXXXXX2125</ns3:String>
<ns4:String xmlns:ns4="http://hps.ws.service/types/">$$$.$$</ns4:String>
<ns5:String xmlns:ns5="http://hps.ws.service/types/">588734</ns5:String>
<ns6:String xmlns:ns6="http://hps.ws.service/types/"></ns6:String>
<ns7:String xmlns:ns7="http://hps.ws.service/types/"></ns7:String>
<ns8:String xmlns:ns8="http://hps.ws.service/types/"></ns8:String>
</args>
</hpsService>
</soapenv:Body></soapenv:Envelope>
08:03:07,889 INFO  [STDOUT] Response Msg = <?xml version='1.0' encoding='UTF-8'?><HPSRESULT><Error>This function is not available</Error></HPSRESULT>
08:03:08,009 INFO  [STDOUT] End Account Enquiry................................

PowerCard will send a response message of an error after 9 minutes saying that this function is not available.
KFH Consumer system time out is 4.5 minutes by default.
According to Hafidzah, the same transaction was retested again around 8.15 am and the transaction was successful since then.
It seemed that the error happen during morning time and starts to work normally after 8.15 am.