IBM Support

LO57770: HTTP CRASH: ERROR - LOCKMEMHANDLE() HANDLE 0XF010D01D IS NOT ALLOCATED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • HTTP Crash with the following stack:
    
    ############################################################
    ### thread 32/61: [   nHTTP:  0358:  0448] FATAL THREAD (Panic)
    ### FP=0x391f8380, PC=0x7c82860c, SP=0x391f8310
    ### stkbase=0x39200000, total stksize=262144, used stksize=31984
    ### EAX=0x00000000, EBX=0x00000000, ECX=0x001d060c,
    EDX=0x001d0608
    ### ESI=0x000011b4, EDI=0x00000000, CS=0x0000001b, SS=0x00000023
    ### DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000
    Flags=0x00000293
    ############################################################
     [ 1] 0x7c82860c ntdll.KiFastSystemCallRet+0
    (11b4,927c0,0,391f8908)
     [ 2] 0x77e61c8d kernel32.WaitForSingleObject+18
    (11b4,927c0,5,391f8b24)
    @[ 3] 0x6020d4bd nnotes.OSRunExternalScript@8+1309 (258,1)
    @[ 4] 0x6020d93f nnotes.FRTerminateWindowsResources+975
    (1,1010,1,0)
    @[ 5] 0x6020dd68 nnotes.OSFaultCleanupExt@24+984
    (f16a68,1010,0,0,0,391f8e4c)
    @[ 6] 0x6020ddea nnotes.OSFaultCleanup@12+26 (0,1010,0)
    @[ 7] 0x60219674 nnotes.OSNTUnhandledExceptionFilter@4+276
    (391f9e84)
    @[ 8] 0x601dad9d nnotes.Panic@4+589 (391f9ea8)
    @[ 9] 0x60002f05 nnotes.LockMemHandle@12+421
    (f010d01d,391f9fcc,0)
    @[10] 0x60002f34 nnotes.OSMemoryUnlock@4+20 (611e9090)
    @[11] 0x600984e4 nnotes.DbGetNamObjDesignEntry@44+4180
    (391fa784,391fa3dc,4e354a88,4,0,391fa39c,f10f10,ffffffff,0,0,0)
    @[12] 0x6009b076 nnotes.DbFindDesignNote+2086
    (391fa784,391fa864,4,0)
    @[13] 0x60099d2e nnotes.iNSFDbFindDesignNote@24+110
    (391fa784,391fa864,4,0,0,391fa760)
    @[14] 0x60099c6b nnotes.NSFDbFindDesignNote@24+107
    (5b0,391fa864,4,0,0,391fa7b8)
    @[15] 0x6009b65e nnotes.FindDesignNote@48+302
    (5b0,391faae4,4,0,0,391faa78,f10f10,ffffffff,0,0,0,0)
    @[16] 0x6009b509 nnotes.NIFFindDesignNoteExt@24+89
    (5b0,391faae4,4,391fabec,0,391faac0)
    @[17] 0x004462a2 ninotes.CmdHandlerBase::OpenWebHybridDbDoc+130
    (4e4ae4b0,4e4bc3cc,391fbd00,4e4ae4b0)
    @[18] 0x0044610e ninotes.CmdHandlerBase::OpenDoc+126
    (4e4ae4b0,4e4bc3cc,1,391fbcf8)
    @[19] 0x0054f1e7 ninotes.Haiku::GetDoc+119
    (391fbcf8,587a03,0,4e4cd1f4)
    @[20] 0x0058246e ninotes.Haiku::GetViewFormDoc+30
    (4e4ae4b0,4e4ae4b0,15304ec,77e620e0)
    @[21] 0x0057ca48 ninotes.Haiku::HandleCmd+904
    (4e4ae4b0,15304ec,0,4e4ae4b0)
    @[22] 0x00445a30 ninotes.CmdHandlerBase::PrivHandle+128
    (4e4ae4b0,0,0,15304ec)
    @[23] 0x0044408d ninotes.CmdHandler::PrivHandle+141
    (4e4ae4b0,4e4ae4b0,4ded50fc,0)
    @[24] 0x00444cc8 ninotes.CmdHandler::Handler+216
    (4e4ae4b0,15304ec,386355c2,391fdebc)
    @[25] 0x0043aa4a ninotes.Cmd::Execute+58
    (367a87c8,367a84d8,367a8c2c,6aecdc)
    @[26] 0x00483a19 ninotes.InotesHTTPProcessRequestImpl+2121
    (367a87d8,367a87c8,367a84d8,367a8c2c)
    @[27] 0x00485fef ninotes.InotesHTTPProcessRequest+47
    (367a87d8,3,391ff5e8,623d5a06)
    @[28] 0x10017cc4 nhttpstack.HTInotesRequest::ProcessRequest+36
    (367a84d8,367a8368,0,391ff9a4)
    @[29] 0x10011f7d
    nhttpstack.HTRequestExtContainer::ProcessRequest+941
    (5,1,3674b004,0)
    @[30] 0x10023f8f nhttpstack.HTRequest::ProcessRequest+1919
    (0,3675ee9e,0,69616d2f)
    @[31] 0x10029777 nhttpstack.HTSession::StartRequest+919
    (3675eeaa,3675ee9e,0,aa0)
    @[32] 0x10030fef nhttpstack.HTWorkerThread::CheckForWork+399
    (14d2ee8,3675ee9e,3,1002d92a)
    @[33] 0x10031558 nhttpstack.HTWorkerThread::ThreadMain+88
    (3675ee9e,0,0,0)
    @[34] 0x601556bf nnotes.ThreadWrapper@4+175 (0)
     [35] 0x77e6482f kernel32.GetModuleHandleA+223
    (60155610,0,0,8000a)
    
    
    PANIC: ERROR - LockMemHandle() Handle 0xF010D01D is not
    allocated
    

Local fix

  • none at this time
    

Problem summary

  • The problem will be fixed in the next release of the product.
    

Problem conclusion

Temporary fix

Comments

  • This APAR is associated with SPR# JPMS8D8N7F.
    The problem will be fixed in the next release of the product.
    

APAR Information

  • APAR number

    LO57770

  • Reported component name

    DOMINO SERVER

  • Reported component ID

    5724E6200

  • Reported release

    852

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-01-18

  • Closed date

    2011-05-02

  • Last modified date

    2011-05-02

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

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:
02 May 2011