Understanding the delay generated from SOAP client-server.
Hi.
I have just upgraded my application from .NET framework to .NET core and one of our SOAP services is having random delays in its responses.
Next is added a snippet of the communication. Package nr 17060 - 17277 are regards a fast response from the server (less than 1s communication between server client.)
However I notice that randomly the server will answer with TCP retransmission as seen in the screenshot below. This exchange delays the entire process by about 20s until a new communication is retried at the package 21798.
Can you make a capture on the server to eliminate the network then begin to work up through the server logs?
@Chuckc Sorry for the miss understanding, we are on control only over the client (were I took the logs). The server is an external services provided to us. Never had this issues beforehand, we have raised some issues with them but they still back up that the communication is good on their end.
As always, please share a pcap file (not a screenshot) on a public file share site and post the link here. A screenshot is terrible to work with.
"upgraded my application" - if nothing has changed on the server, how does the client app behave differently now after the upgrade? Is it making more requests to the server which might cause the server to run out of resources? Can you go back to the old application, make a baseline of network activity and compare that to new app?
Are there many clients doing SOAP requests to the remote service? Which device is doing the NAT and are you able to make a capture on the public side of the NAT?