APAR status
Closed as Vendor Solution.
Error description
When performing a large number of ClearCase operations on Window s Vista Business/Enterprise SP1, '[WINSOCK] invalid argument' er rors may intermittently occur.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
The Windows Vista issue we encountered has to do with how Vista reacts when a new process attempts to bind to a port in use by an existing process running on the same host. Windows XP and Vista SP2 throw an error that the port number is in use, forcing our software to choose a new port. We then try the next port and, if available, we bind to that port and use it to communicate with the server process (local or remote). With the unpatched Vista client, when we try to bind to an existing port, we still get the error that the port is in use, but when we try to bind to a different port, Vista reports the "Invalid argument" error and appears to trash the socket we had initially opened for the bind (no socket operations are possible any longer after the first bind failure). This appears to have been fixed by Vista Service Pack 2.
APAR Information
APAR number
PK99798
Reported component name
CLEARCASE WIN
Reported component ID
5724G2900
Reported release
700
Status
CLOSED ISV
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-10-28
Closed date
2009-11-19
Last modified date
2009-11-19
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
19 November 2009