IBM Support

PM47364: Project Explorer may crash when rebasing a very long list of baselines

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When rebasing a very long list of baselines in IBM Rational
    ClearCase Project Explorer, the application may crash.
    
    Although this is only likely to be seen with a very large number
    of baselines, the cause is not with the actual number of
    baselines specifically, but with the string length of the list
    of baselines in aggregate.
    
    When performing the rebase, a command such as the following will
    be made:
    
    -----
    clearmrgman /rebase /stream stream:dev@\IBMtestpvob /bls
    baseline:LB-IBMtest_IBMtest_comp001_IMPORT@\IBMtestpvob
    baseline:LB-IBMtest_IBMtest_comp002_IMPORT@\IBMtestpvob
    baseline:LB-IBMtest_IBMtest_comp003_IMPORT@\IBMtestpvob
    baseline:LB-IBMtest_IBMtest_comp004_IMPORT@\IBMtestpvob ...
    -----
    
    When the total length of this string reaches 32,767 or higher,
    Project Explorer has been seen to crash.
    
    In the above example, it would take 585 baselines being rebased
    before this problem could occur.
    
    Steps to reproduce the issue:
    
    1) Create a new IBM Rational ClearCase Unified Change Management
    (UCM) Project VOB (pvob) named 'IBMtestpvob'.
    
    2) Create a new UCM project in this pvob.
    
    3) Create 650 components, with a naming convention of
    'IBMtest_Comp###'.
    
    4) Seed the integration stream with the initial baseline of each
    component.
    
    5) Create a child development stream.
    
    6) On the integration stream, add one file to source control for
    each component.
    
    7) Create a new baseline for each component, using the naming
    convention 'IBMtestBaseline###_IBMtest_Comp###'.
    
    8) Rebase the development stream to the new baselines.  The
    application will crash.
    
    
    WORKAROUND:
    
    A) Use composite baselines to organize multiple components and
    reduce the number of baselines being rebased.   This is the
    recommended workaround.
    
    B) Shorten each baseline name to ensure the baseline list is
    under 32,767 characters.
    
    C) Shorten the pvob tag.  For every one character removed from
    the pvob tag, the total character string will be reduced by that
    amount multiplied by the number of baselines.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When rebasing a very long list of baselines in IBM Rational
    ClearCase Project Explorer, the application may crash.
    
    Although this is only likely to be seen with a very large
    number of baselines, the cause is not with the actual number
    of baselines specifically, but with the string length of the
    list of baselines in aggregate.
    
    When performing the rebase, a command such as the following
    will be made:
    
    -----
    clearmrgman /rebase /stream stream:dev@\IBMtestpvob /bls
    baseline:LB-IBMtest_IBMtest_comp001_IMPORT@\IBMtestpvob
    baseline:LB-IBMtest_IBMtest_comp002_IMPORT@\IBMtestpvob
    baseline:LB-IBMtest_IBMtest_comp003_IMPORT@\IBMtestpvob
    baseline:LB-IBMtest_IBMtest_comp004_IMPORT@\IBMtestpvob ...
    -----
    
    When the total length of this string reaches 32,767 or
    higher, Project Explorer has been seen to crash.
    
    In the above example, it would take 585 baselines being
    rebased before this problem could occur.
    
    Steps to reproduce the issue:
    
    1) Create a new IBM Rational ClearCase Unified Change
    Management (UCM) Project VOB (pvob) named "IBMtestpvob".
    
    2) Create a new UCM project in this pvob.
    
    3) Create 650 components, with a naming convention of
    "IBMtest_Comp###".
    
    4) Seed the integration stream with the initial baseline of
    each component.
    
    5) Create a child development stream.
    
    6) On the integration stream, add one file to source control
    for each component.
    
    7) Create a new baseline for each component, using the
    naming convention "IBMtestBaseline###_IBMtest_Comp###".
    
    8) Rebase the development stream to the new baselines. The
    application will crash.
    
    
    WORKAROUND:
    
    A) Use composite baselines to organize multiple components
    and reduce the number of baselines being rebased.   This is
    the recommended workaround.
    
    B) Shorten each baseline name to ensure the baseline list is
    under 32,767 characters.
    
    C) Shorten the pvob tag.  For every one character removed
    from the pvob tag, the total character string will be
    reduced by that amount multiplied by the number of
    baselines.
    

Problem conclusion

  • A fix is available in ClearCase versions 7.1.1.8, 7.1.2.5
    and 8.0.0.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM47364

  • Reported component name

    CLEARCASE WIN

  • Reported component ID

    5724G2900

  • Reported release

    711

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-09-07

  • Closed date

    2011-12-16

  • Last modified date

    2011-12-16

  • 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

    CLEARCASE WIN

  • Fixed component ID

    5724G2900

Applicable component levels

  • R711 PSN

       UP

[{"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.1.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
16 December 2011