LO73831: PANIC: OBJECT HANDLE IS INVALID

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

  • 1* Server crash on http task with PANIC: Object handle is￴
    invalid
    
    
    ############################################################
    
    ### thread 26/67: [   nhttp:  088c:  05b8] FATAL THREAD (Panic)
    
    ### FP=0x607203f8, PC=0x771e135a, SP=0x607203f8
    
    ### stkbase=0x60730000, total stksize=4194304, used
    stksize=64520
    ### EAX=0x00000041, EBX=0x00000000, ECX=0x6071f3d2,
    EDX=0x7FE9CD942C7
    ### ESI=0x000dbba0, EDI=0x00001060, CS=0x00000033,
    SS=0x7FE0000002B
    ### DS=0x00000000, ES=0x00000000, FS=0x00000000,
    GS=0x7FE00000000
    Flags=0x00000287
    
    ############################################################
    
     [ 1] 0x771e135a ntdll.ZwWaitForSingleObject+10
    
    (FE5A8CCF324C,30a47b9,3,4b27fc0)
    
     [ 2] 0x7FEFD7A10DC KERNELBASE.WaitForSingleObjectEx+156
    (5,5,0,1060)
    @[ 3] 0x00ea584b nnotes.FRSendCommandToService+1943
    
    (60725a70,60725d88,0,ea1b34)
    
    @[ 4] 0x00ea9134 nnotes.OSRunExternalScript+5860
    (3,5,311c0a4,1)
    @[ 5] 0x00ea2961 nnotes.FRTerminateWindowsResources+2277
    
    (1,771b920c,af,60727260)
    
    @[ 6] 0x00eac0fe nnotes.OSFaultCleanupExt+622
    (0,ea1cfb,150014,31201d0)
    @[ 7] 0x00eacb75 nnotes.OSFaultCleanup+29 (35,34,39daf40,2c)
    
    @[ 8] 0x00ec64ea nnotes.OSNTUnhandledExceptionFilter+626
    
    (60728d00,3103184,60728700,30)
    
    @[ 9] 0x00e3626b nnotes.Halt+923 (200005cb,1009,0,0)
    
    @[10] 0x0252a180 nnotes.HANDLEDereference+112
    (60728ec0,20645bf,80d,2)
    @[11] 0x0252ac0d nnotes.HANDLEDereferenceToNSFBLOCK+9
    
    (0,1009,0,30071200)
    
    @[12] 0x02570cf0 nnotes.InitDbContextExt+292
    (93d72,0,200005cb,2d3)
    @[13] 0x02570df3 nnotes.InitDbContext+15 (0,3007140c,2d3,93d72)
    
    @[14] 0x0256bde2 nnotes.NSFDbUserGetbServer+18 (0,0,0,ffffffff)
    
    @[15] 0x01ddfaea nnotes.ClientDbGetBuildVersion+18
    
    (8e00004,2ee57bf,87900001,99f00001)
    
    @[16] 0x01dc2d3e nnotes.ReceiveNoteAsync+3442
    
    (49800004,8e00004,1806A000000000,e46a1a)
    
    @[17] 0x01de011a nnotes.ClientNoteOpen+1234
    
    (100000000,607294d8,6655265746F4E24,65636E657265)
    
    @[18] 0x023df255 nnotes.iNSFNoteOpenExtended3+265
    
    (60720040,2d3,93d72,7000002)
    
    @[19] 0x025891d4 nnotes.NSFNoteOpenExt+1768
    
    (0,5abf6818,60729570,5a8cf2ee)
    
    @[20] 0x5a83ea23 nlsxbe.ANNote::ANNOpenNote+127
    
    (5abf6818,0,7FFC3D07880,57ed54c)
    
    @[21] 0x5a7e5cfc nlsxbe.ANDatabase::ANDFindNote+912
    
    (5ac897f8,6cce7418,93d72,5aa875b8)
    
    @[22] 0x5a80c8e6
    
    nlsxbe.Java_lotus_domino_local_Database_NgetDocumentByID+398
    
    (57f59800,6cce7420,6cce7418,7FFC34FC528)
    

Local fix

  • looks like an application problem exposed some sort of weakness￴
    in our  api.
    
    Perhaps an InitDbContextExt instead of an InitDbContext.
    
    Customer have done some changes in the design (while accessing
    the mailfiles from the Java code). Since this changes the
    server is stable,
    

Problem summary

  • Follow up KMUR94NJPQ fix by adding additional initialization to
     NULL on  *bServer on err return
    

Problem conclusion

  • Follow up KMUR94NJPQ fix by adding additional initialization to
     NULL on  *bServer on err return
    

Temporary fix

Comments

  • This APAR is associated with SPR# KMUR94NJPQ.
    Follow up KMUR94NJPQ fix by adding additional initialization to
     NULL on  *bServer on err return
    

APAR Information

  • APAR number

    LO73831

  • Reported component name

    DOMINO SERVER

  • Reported component ID

    5724E6200

  • Reported release

    853

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-06

  • Closed date

    2014-10-28

  • Last modified date

    2014-10-28

  • 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

  • R853 PSN

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Domino

Software version:

8.5.3

Reference #:

LO73831

Modified date:

2014-10-28

Translate my page

Machine Translation

Content navigation