This content has been marked as final. Show 2 replies
Sorry for the late response.
With the new patch in place do you see the same problem on subsequent requests for the same patch?
When you restarted the server did you check for old processes that might have been leftover?
Note that we have been testing an IDR for the patch server, which will hopefully be released soon.
Our local patch server actually has a T-patch, T119788-10, applied now. The problem mentioned
here occurred after application of that patch. It seemed to happen only when many patch clients
connected to the patch server at the same time, and when they all needed to download a large
number of patches. This only happens periodically, when a new batch of patches is released.
It didn't happen in the few weeks after application of the T-patch.
The behavior is somewhat unpredictable. Once it had happened, it seemed to happen each time
on the same client, even though the server was idle. Restarting the patch server had no effect,
but removing the file on the patch server caused it to work again.
The problem of leftover processes seems to have been solved by the T-patch.