IBM Support

IV72169: OUTOFMEMORY IN DISCOVER JVM DUE TO ISSUE WITH MINDTERM : [CRYPTZONE #1806] MEMORY LEAK - SUSPECTED SWITCHBOARD._CHANNELS

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

  • In TADDM 7.3.0 Discover JVM may run out of
    memory(OOM/OutOfMemory) during discovery.  A sample stack trace
    is below. This issue is fixed in FP1, which includes
    an updated MindTerm which should fix the leaks when receiving
    read failures during initial handshake/key setup. It will also
    remove various invalid/duplicated error/debug messages when
    connections are being closed down.
    
    2015-04-08 14:02:56,887 DiscoverManager [AgentSelector-0]  ERROR
    worker.AgentSelector -
    java.lang.OutOfMemoryError: Java heap space
            at
    java.lang.StringBuilder.ensureCapacityImpl(StringBuilder.java:34
    2)
            at
    java.lang.StringBuilder.append(StringBuilder.java:208)
            at
    java.io.ObjectStreamField.getClassSignature(ObjectStreamField.ja
    va:331)
            at
    java.io.ObjectStreamField.<init>(ObjectStreamField.java:151)
            at
    java.io.ObjectStreamClass.getDefaultSerialFields(ObjectStreamCla
    ss.java:
    1737)
            at
    java.io.ObjectStreamClass.getSerialFields(ObjectStreamClass.java
    :1653)
            at
    java.io.ObjectStreamClass.access$800(ObjectStreamClass.java:85)
            at
    java.io.ObjectStreamClass$3.run(ObjectStreamClass.java:563)
            at
    java.io.ObjectStreamClass$3.run(ObjectStreamClass.java:549)
            at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:274)
            at
    java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:549)
            at
    java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:393)
    
    
    
    
    Memory analyzer provides details linkingthe issue to MindBright;
    
    
    One instance of "java.util.Hashtable$Entry[]" loaded by "<system
     class loader>" occupies 385,932,640 (39.01%) bytes. The
    instance is referenced by com.mindbright.nio.Switchboard @
    0x589bf478 , loaded by "<system class loader>". The memory is
    accumulated in one instance of "java.util.Hashtable$Entry[]"
    loaded by "<system class loader>".
    

Local fix

Problem summary

  • In TADDM 7.3.0 Discover JVM may run out of
    memory(OOM/OutOfMemory) during discovery.  A sample stack trace
    is below. This issue is fixed in FP1, which includes
    an updated MindTerm which should fix the leaks when receiving
    read failures during initial handshake/key setup. It will also
    remove various invalid/duplicated error/debug messages when
    connections are being closed down.
    
    2015-04-08 14:02:56,887 DiscoverManager íAgentSelector-0ù  ERROR
    worker.AgentSelector -
    java.lang.OutOfMemoryError: Java heap space
            at
    java.lang.StringBuilder.ensureCapacityImpl(StringBuilder.java:34
    2)
            at
    java.lang.StringBuilder.append(StringBuilder.java:208)
            at
    java.io.ObjectStreamField.getClassSignature(ObjectStreamField.ja
    va:331)
            at
    java.io.ObjectStreamField.<init>(ObjectStreamField.java:151)
            at
    java.io.ObjectStreamClass.getDefaultSerialFields(ObjectStreamCla
    ss.java:
    1737)
            at
    java.io.ObjectStreamClass.getSerialFields(ObjectStreamClass.java
    :1653)
            at
    java.io.ObjectStreamClass.access$800(ObjectStreamClass.java:85)
            at
    java.io.ObjectStreamClass$3.run(ObjectStreamClass.java:563)
            at
    java.io.ObjectStreamClass$3.run(ObjectStreamClass.java:549)
            at
    java.security.AccessController.doPrivileged(AccessController.jav
    a:274)
            at
    java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:549)
            at
    java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:393)
    
    
    
    
    Memory analyzer provides details linkingthe issue to MindBright;
    
    
    One instance of "java.util.Hashtable$Entryíù" loaded by "<system
    class loader>" occupies 385,932,640 (39.01%) bytes. The
    instance is referenced by com.mindbright.nio.Switchboard @
    0x589bf478 , loaded by "<system class loader>". The memory is
    accumulated in one instance of "java.util.Hashtable$Entryíù"
    loaded by "<system class loader>".
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    packages:
    | Fix Pack | 7.3.0-TIV-ITADDM-FP0002
    Check the IBM Software Support web site for availability of the
    above maintenance packages.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV72169

  • Reported component name

    APP DEPENDENCY

  • Reported component ID

    5724N5500

  • Reported release

    730

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-04-14

  • Closed date

    2015-05-06

  • Last modified date

    2015-05-06

  • 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

    APP DEPENDENCY

  • Fixed component ID

    5724N5500

Applicable component levels

  • R730 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSPLFC","label":"Tivoli Application Dependency Discovery Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"730","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
06 May 2015