IBM Support

IV19631: JVM CONTAINING MANY MONITORS AND THREADS IS SLOW TO WRITE A JAVA CORE.TXT FILE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Message: N/A
    .
    Stack Trace: N/A
    .
    The JVM takes a long time to generate a javacore.txt file when
    one is requested. This problem typically occurred when JVM has
    hundreds of threads running and tens of thousands of monitors.
    

Local fix

Problem summary

  • This was a performance issue while producing the information for
    the LOCKS section of the javacore.txt report.
    One particular case was caused by the presence of hundreds of
    threads and tens of thousands of classloaders each of which had
    an associated monitor however monitors may be created for other
    reasons.
    

Problem conclusion

  • This defect will be fixed in:
    6.0.1 SR2
    7.0.0 SR1
    .
    The JVM has been updated to gather this information more
    efficiently.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV19631

  • Reported component name

    J9 COMMON CODE

  • Reported component ID

    620700127

  • Reported release

    260

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-04-12

  • Closed date

    2012-04-12

  • Last modified date

    2012-04-12

  • 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

    J9 COMMON CODE

  • Fixed component ID

    620700127

Applicable component levels

  • R260 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
22 February 2022