PM51958: DiffMerge tool crashes at 2GB memory footprint when we perform a Sync using Gateway.

Rational Rhapsody 8.0.5
Rational Rhapsody Fix Pack 5 (7.6.1.5) for 7.6.1
Rational Rhapsody 8.0.6

APAR status

• Closed as program error.

Error description

• Summary:
  *********
  
  DiffMerge tool crashes at 2GB memory footprint when we perform a
  Sync using Gateway.
  
  Description:
  **********
  
  Client is using the Gateway tool to synchronise requirements
  into a large SysML model and wants to do so with support from
  DiffMerge. When they try this, the DiffMerge tool starts,
  increases its memory footprint to 2GB and crashes. It looks like
  their model is too large and DiffMerge cannot handle it.
  
  As diffmerge already provides the functionality to merge model
  unit by unit similar to way clearcase/synergy merge managers do,
  it looks like this is a problem by Gateway as it passes the
  entire model to DiffMerge in this scenario. Ideally, gateway
  should perform merge unit by unit rather than whole model.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Now it is possible to invoke DiffMerge successively on all
  units instead of the complete model.
  
  This could allow to get rid of the DiffMerge crash.
  
  
  
  This behavior can be only activated with the environment
  variable SYNC_INDIVIDUAL_MERGE since this is just some kind
  of workaround.
  
  It is also suggested to activate 'Try to merge
  automatically' in sync options otherwise you will have to
  save the merge result manually for all units.
  
  
  
  Limitation:
  
  The non-recursive mode of DiffMerge cannot detect conflicts
  when a package is removed but the content of the same
  package was modified.
  
  The result is that DiffMerge is that removes the package
  from the parent unit since there is no conflict at this
  place.
  

Problem conclusion

• Fixed in 8.0.5
  

Temporary fix

Comments

APAR Information

• 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

  TLOGIC RHAPSODY

• Fixed component ID

  5724V74RP

Applicable component levels

• R753 PSN

     UP