IBM Support

IV20277: JAVA EXECUTABLE FAILS TO LAUNCH ON WINDOW OS THAT SUPPORT NUMA A ND HAVE MULTIPLE NUMA NODES.

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
    .
    This issue occurs on Windows OS that support NUMA and have
    multiple NUMA nodes.  A dialog opens with the following message
    "Java(TM) Platform SE binary has stopped working", when
    attempting to run the java executable indicating that it failed
    to launch.
    

Local fix

Problem summary

  • The issue was seen in the case where the OS supports NUMA
    (Non-Uniform Memory Access) and has more than one NUMA node
    present.  The problem was that the internal representation of
    the NUMA node details was not being properly populated.
    

Problem conclusion

  • This defect will be fixed in:
    7.0.0 SR1
    6.0.1 SR2
    .
    The internal representation of the NUMA node details is now
    being properly filled in, in the case where there are multiple
    NUMA nodes supported.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV20277

  • 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-26

  • Closed date

    2012-04-26

  • Last modified date

    2012-04-26

  • 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