IBM Support

PM76509: Shipping server needs to account for Windows 'deferred bind on connect' behavior when strict port allocation in use.

Fixes are available

Rational ClearQuest Fix Pack 10 (7.1.2.10) for 7.1.2
Rational ClearCase Fix Pack 10 (7.1.2.10) for 7.1.2
Rational ClearQuest Fix Pack 06 (8.0.0.6) for 8.0
Rational ClearCase Fix Pack 06 (8.0.0.6) for 8.0
Rational ClearCase Fix Pack 14 (7.1.2.14) for 7.1.2
Rational ClearCase Fix Pack 11 (8.0.0.11) for 8.0
Rational ClearQuest Fix Pack 14 (7.1.2.14) for 7.1.2
Rational ClearQuest Fix Pack 11 (8.0.0.11) for 8.0
Rational ClearCase Fix Pack 12 (8.0.0.12) for 8.0
Rational ClearCase Fix Pack 15 (7.1.2.15) for 7.1.2
Rational ClearQuest Fix Pack 12 (8.0.0.12) for 8.0
Rational ClearQuest Fix Pack 15 (7.1.2.15) for 7.1.2
Rational ClearCase Fix Pack 13 (8.0.0.13) for 8.0
Rational ClearCase Fix Pack 16 (7.1.2.16) for 7.1.2
Rational ClearQuest Fix Pack 13 (8.0.0.13) for 8.0
Rational ClearQuest Fix Pack 16 (7.1.2.16) for 7.1.2
Rational ClearQuest Fix Pack 17 (7.1.2.17) for 7.1.2
Rational ClearCase Fix Pack 17 (7.1.2.17) for 7.1.2
Rational ClearQuest Fix Pack 14 (8.0.0.14) for 8.0
Rational ClearCase Fix Pack 14 (8.0.0.14) for 8.0
Rational ClearQuest Fix Pack 18 (7.1.2.18) for 7.1.2
Rational ClearCase Fix Pack 18 (7.1.2.18) for 7.1.2
Rational ClearQuest Fix Pack 15 (8.0.0.15) for 8.0
Rational ClearCase Fix Pack 15 (8.0.0.15) for 8.0
Rational ClearQuest Fix Pack 19 (7.1.2.19) for 7.1.2
Rational ClearCase Fix Pack 19 (7.1.2.19) for 7.1.2
Rational ClearQuest Fix Pack 16 (8.0.0.16) for 8.0
Rational ClearCase Fix Pack 16 (8.0.0.16) for 8.0
Rational ClearQuest Fix Pack 17 (8.0.0.17) for 8.0
Rational ClearCase Fix Pack 17 (8.0.0.17) for 8.0
Rational ClearQuest Fix Pack 18 (8.0.0.18) for 8.0
Rational ClearCase Fix Pack 18 (8.0.0.18) for 8.0
Rational ClearQuest Fix Pack 19 (8.0.0.19) for 8.0
Rational ClearCase Fix Pack 19 (8.0.0.19) for 8.0

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When using the IBM Rational ClearCase MultiSite shipping server
    in a firewall-enabled configuration with strict outbound port
    allocation on Microsoft Windows 2008 R2 Server, connection
    errors may occur, causing hosts to be incorrectly flagged as
    down.
    
    This issue is caused by a new Windows Sockets behavior in the
    most recent version of Microsoft Windows.
    
    The current workarounds are:
    1) Do not use MSSHP_STRICT port allocation.
    2) Use a Unix or Linux host to provide firewall-compatible
    shipping server services.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    shipping server fails on connect command even if with a
    valid binding port
    

Problem conclusion

  • A fix is available in ClearCase versions 7.1.2.10 and
    8.0.0.6
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM76509

  • Reported component name

    CLRCASE MSITE W

  • Reported component ID

    5724G3200

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-05

  • Closed date

    2013-03-20

  • Last modified date

    2013-03-20

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    CLRCASE MSITE W

  • Fixed component ID

    5724G3200

Applicable component levels

  • R800 PSN

       UP



Document information

More support for: Rational ClearCase MultiSite

Software version: 8.0

Reference #: PM76509

Modified date: 20 March 2013