IBM Support

IV87060: UNABLE TO ANALYSE AIX NODE.JS CORE DUMPS WITH IDDE TOOLING

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

  • Error Message: Problem running command:
    com.ibm.j9ddr.NullPointerDereference: Memory Fault reading
    0x00000000 :
    .
    Stack Trace: com.ibm.j9ddr.NullPointerDereference: Memory Fault
    reading 0x00000000 :
             at
    com.ibm.j9ddr.node4.pointer.generated.v8.internal.HeapPointer.ro
    ots_EA(HeapPointer.java:1545)
             at
    com.ibm.j9ddr.node4.helpers.HeapObject.isHashTable(HeapObject.ja
    va:287)
             at
    com.ibm.j9ddr.node4.helpers.HeapObject.isDictionary(HeapObject.j
    ava:293)
             at
    com.ibm.j9ddr.node4.helpers.JSObject.hasFastProperties(JSObject.
    java:137)
             at
    com.ibm.j9ddr.node4.helpers.JSObject.getProperties(JSObject.java
    :201)
             at
    com.ibm.java.diagnostics.idde.commands.ddr.node.node4.NodeBuffer
    sCommand.subrun(NodeBuffersCommand.java:97)
             at
    com.ibm.java.diagnostics.commands.ddr.BaseDDRCommand.run(BaseDDR
    Command.java:104)
             at
    com.ibm.java.diagnostics.utils.Context.tryCommand(Context.java:1
    95)
             at
    com.ibm.java.diagnostics.utils.Context.tryCommand(Context.java:2
    34)
             at
    com.ibm.j9ddr.plugins.DDRContext.execute(DDRContext.java:175)
             at
    com.ibm.java.diagnostics.idde.system.CombinedContext.execute(Com
    binedContext.java:336)
             at
    com.ibm.java.diagnostics.idde.system.SessionJob.execute(SessionJ
    ob.java:60)
             at
    com.ibm.java.diagnostics.idde.system.WorkerThread.processQueue(W
    orkerThread.java:74)
             at
    com.ibm.java.diagnostics.idde.system.WorkerThread.run(WorkerThre
    ad.java:55)
    .
    This problem will not affect Node.js runtime
    functionality/capability for executing applications, but
    compromises post-mortem analysis (and our serviceability) with
    our IBM diagnostic tooling if the unforeseen happens and the
    process should crash.
    

Local fix

Problem summary

  • The problem was caused by a mistake made when creating the 4.X.X
    build job, resulting in the BLOb meta-data for a different
    platform being included in the AIX Node.js build.  Some IDDE
    commands were working, but others were completely or partially
    broken (including nodebuffers, which produced the error shown
    above).
    

Problem conclusion

  • Our build step, packaging the correct architecture component,
    has been corrected.
    .
    This APAR will be fixed in the following IBM SDK for Node.js
    Releases:
       4.4.6.0
    .
    Contact your IBM Product's Service Team for these Service
    Refreshes and Fix Packs.
    For those running stand-alone, information about the available
    Service Refreshes and Fix Packs can be found at:
               http://www.ibm.com/developerworks/web/nodesdk/
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV87060

  • Reported component name

    NODE.JS

  • Reported component ID

    AIMNDJS00

  • Reported release

    421

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-19

  • Closed date

    2016-07-19

  • Last modified date

    2016-07-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

    NODE.JS

  • Fixed component ID

    AIMNDJS00

Applicable component levels

  • R421 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSWLKB","label":"IBM SDK for Node.js"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"421","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
11 February 2022