Slow response when first initiating a server request IPV6

[robe070]

Hi,

We've resolved this issue already. This is just to be of help for anyone else who might come across the issue.

We noticed that operations like check out, or diffs or History would take up to 30 seconds the first time we tried it and then be almost instantaneous the 2nd and subsequent. If we left it for 5 mins or so, it would be back to the delay.

We turned on client tracing and found out it was taking all its time to perform GetRepositoryStructure.

We then turned on the Server logging and found out that it did not receive anything for most of the delay period.

We then used Process Monitor to watch the activity of the Vault Client. It was hardly doing anything, particularly no file access, except TCP/IP comms of which the whole delay was during IPV6 comms.

When we pinged the Vault Server it timed out using the IPV6 address.

IPV6 was not installed on the server. We looked in the DNS and there was an IPV6 address assigned to the server. We deleted it. Ping now used an IPV4 address and worked.

The Vault delay stopped occurring.

[Beth]

Thank you for posting the information.