Our application is using Connect REST to connect an external system. Though the service is returning the response when it receives the request in milli seconds, Pega is taking more time to hit the service layer.
When I run tracer, I can see the waiting time is at step 5 of InvokeRESTConnector activity. When db query/activity steps turned on, the step 5 beginning starts at lets say: 12:10:25 pm, the service layer is getting the request at 12:10:34 and response obtained at 12:10:35. 9+ seconds are spent during this. Did anyone face the same issue?
Yes. We tested with soap UI and postman. Results are returned within milli seconds though the first call takes time. I mentioned the step which is taking 9+seconds as we are not supposed to share logs.
Installed wireshark monitoring tool in the server and We monitored the tcp dumps. Network team informed that the PTR[PTR records are used for the Reverse DNS (Domain Name System) lookup] is found in the dump and application needs to stop doing this.
I created a SR last month but the team said, there is no 'Host name resolution' done in pega side. Not sure if this is pega issue. But if someone experienced such latency and fixed the issue- pls advice.