|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
How to "Capture the HTTP request and response headers"?
We did get below summary from our IT when asking them to investigating this issue(we thought it was about network before):
Our networking team have run a few captures from the host you provided (10.62.34.216) using Wireshark while downloading the platypus.exe file. There seems to be duplicate requests where a packet is trying re-sending over and over (sometimes up to 120 times). This happens both when the file is loaded with a lower MB size and even when the file loads the entire 472MB.
We also ran Wireshark captures from two separate desktops on our end and received no duplicate packet requests and a complete download. This is leading us to believe that there is isn’t a problem on the web server and that there may be a problem on the hosts in your network blocking traffic. Ronald took a look at the captures and does see a huge amount of duplicate ack packets. His report was these are requests from the receiver side towards the server asking for the server to resend a specific packet/frame that is missing. Normally, the server sees around 3 of these and immediately resends the packet the missing packet. This could point to packet loss problem but further captures and data would help us to verify this. Below is a image of the capture(see attachment wireshark log).
As our network team see no abnormal in network, we did the experiments and found this issue is not exist on 1.532.3, but exist on 1.565.2. So we can say that it should be a jenkins issue, but this issue might be triggered by network that has a big latency.