IBM Support

JR57672: <NODE_DIR>\WSTEMP LEAKS (AND POTENTIAL OUTOFMEMORY SCENARIOS) CONTINUE FOR POLICYSET AND BINDNG COMMANDS

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • There have been past interim fixes created to keep the \wstemp
    directories for the NODEs and the DMGR cleaned up for PolicySet
    and Binding commands. However under certain conditions that
    appear to be related to the client's use of custom AdminClients
    with the CommandMgr command, these \wstemp leaks persist,
    typically causing a proliferation of liPoSet*, liPoBid* and
    psLPTp* directories in \wstemp.
    
    This issue can also potentially cause OutOfMemory scenarios,
    where the leak suspect may match the following:
    
    The class "com.ibm.ws.sm.workspace.WorkSpaceManagerFactory",
    loaded by "<system class loader>", occupies xxx (yy%) bytes.
    The memory is accumulated in one instance of
    "java.util.HashMap$Entry[]" loaded by "<system class loader>".
    Keywords
    java.util.HashMap$Entry[]
    com.ibm.ws.sm.workspace.WorkSpaceManagerFactory
    
    The following operations have been confirmed to use the
    affected code:
    1) Runtime: Invoke of a WebService Integration(WSI) (in BPM
    Std) using PolicySet and Binding
    2) Runtime: Invoke of a WebService Binidng (in BPM Adv) using
    PolicySet and Binding
    3) Development: Clicking browse for PolicySet and Binding in
    Process Designer (inline or server configuration)
    4) Development: Clicking browse for PolicySet and Binidng in
    Integration Designer
    5) Administration: Using the Process Admin Console and
    reviewing a Server Configuration for a WSI.
    
    JR57672 will now complement all the previous interim fixes, and
    the \wstemp directories for both the NODEs and DMGR will now be
    discarded correctly.
    

Local fix

  • As a temporary workaround at the NODE level, stop the NODE,
    delete the liPoSet*, liPoBid* and psLPTp* directories in
    \wstemp, and then restart this NODE. The same steps can be
    followed at the DMGR level if necessary.
    

Problem summary

  • No additional information is available.
    
    PRODUCTS AFFECTED
    IBM Business Process Manager (BPM) Advanced
    IBM BPM Standard
    IBM BPM Express
    

Problem conclusion

  • A fix is available for IBM BPM V8.5.6.0 cumulative fix 2 that
    avoids the local \wstemp leak for PolicySet and Binding
    commands.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR57672

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    856

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-29

  • Closed date

    2017-06-12

  • Last modified date

    2017-09-19

  • 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

  • R856 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":"856","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
19 September 2017