IBM Support

LO78867: XPAGES: 'XSPDOC.GETDOCUMENT()' IS NULL

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

  • When two Xpages are executing SSJS code involving datasource
    documents, one datasource doc could eventually end up losing
    scope and returning null.
    
    I am providing a sample nsf for reproducing and I have tested
    in 9.0 and 8.5.3 FP4.
    
    The sample code to test this issue is basically this:
    
    for (var i = 0; i < 50000; i++ ) {
      counter++;
      comment = xspDoc.getDocument().getItemValue("COMText");
    }
    
    In my testing, counter would get up to roughly 12000 before
    getDocument returns null. This seems to be entirely based on
    the timing of running two different Xpages simultaneously.
    
    Steps to reproduce:
    
    1. Get nsf file from attachments database
    2. Place nsf on Domino server and make sure to sign all design
    elements
    3. Open the byDealId view and click on "Open iFrames" button.
    Note: In this test case, both Xpages will run inside an iFrame,
    but the same call stack was reproduced without using iFrames in
    a similar test case.
    4. Next you will need to press both "Edit" buttons as quickly
    as possible so that both will be executing at the same time.
    You will reproduce the issue when one of the documents do not
    go into edit mode.
    5. You can view the error condition within a Notes document
    that is created in the nsf in the Error view "byDate". Just
    look for the date/time you tested the issue.
    

Local fix

  • LOCAL FIX:
    none
    

Problem summary

  • A programming error was found and will be corrected in a future
     release.
    

Problem conclusion

  • A programming error was found and will be corrected in a future
     release.
    

Temporary fix

Comments

  • This APAR is associated with SPR# RPEA9FU2NH.
    A programming error was found and will be corrected in a future
     release.
    

APAR Information

  • APAR number

    LO78867

  • Reported component name

    DOMINO SERVER

  • Reported component ID

    5724E6200

  • Reported release

    852

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-01-29

  • Closed date

    2014-05-27

  • Last modified date

    2014-05-27

  • 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

    DOMINO SERVER

  • Fixed component ID

    5724E6200

Applicable component levels

  • R852 PSN

       UP

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSKTMJ","label":"Lotus Domino"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
27 May 2014