IBM Support

JR57310: REQUIRE CONFIGURATION POINT TO MANAGE COACH STAGE1 GENERATION CACHE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The <coach-generation-config> property should allow you to
    manage cache size, specifically for coach stage 1 generation, so
    that you can reduce memory consumption and avoid out-of-memory
    errors on the IBM Business Process Manager (BPM) server.
    
    PRODUCTS AFFECTED:
    IBM BPM Advanced
    IBM BPM Standard
    IBM BPM Express
    

Local fix

  • Restart the server.
    

Problem summary

  • No additional information is available.
    

Problem conclusion

  • A fix will be included in IBM BPM V8.5.7 cumulative fix 2017.03
    that provides a configuration point to manage the stage 1 coach
    generation cache.
    
    The following comment will be added to the 99Local.xml file
    about how to manage the coach generation cache.
    
      <!--
       The configuration <coach-generation-config> has the following
    3 properties that can be set.
       1. If <enable-cache-management> is set to true, this property
    enables the management of the cache size for the stage 1 coach
    generation details
       2. The property <cache-max-size> sets the maximum cache size,
    this is the number of stage 1 coach generation details to retain
       3. The property <cache-removal-amount> sets the number of
    stage 1 coach generation details to remove when the max size is
    reached
      -->
      <!--
      <coach-generation-config>
       <enable-cache-management>true</enable-cache-management>
    
       <cache-max-size>256</cache-max-size>
    
       <cache-removal-amount>12</cache-removal-amount>
      </coach-generation-config>
      -->
    
    As a by-product of adding the support for the
    <coach-generation-config> property, the used variables of a
    coach are now stored in the http session similar to the coach
    HTML content, which allows the coach generation details to be
    removed from the cache and regeneration to occur, if requested,
    in the future.
    
    In addition, more tracing was added for the following methods:
    
    com.lombardisoftware.component.coach.data.CoachDataBindingHelper
    .getTeamDeclaration()
    com.lombardisoftware.component.coachng.worker.CoachNGWorker.doJo
    bProcessWebData()
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR57310

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    857

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-02-06

  • Closed date

    2017-02-06

  • Last modified date

    2017-03-09

  • 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

    BPM ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R857 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"857","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
09 March 2017