LO51863: LKMGR TIMEOUTS DUE TO SCHED TASK

APAR status

• Closed as fixed if next.

Error description

• The Domino server became unresponsive and generated repeated
  lkmgr timeouts on
  a mailfile.
  This was a one time incident of this nature.
  The holding sched thread was 1237186:00002-00001:
  
  [1130512:00073-17734] LkMgr BEGIN Long Held Lock Dump
  ------------------
  [1130512:00073-17734] Lock(Mode=S  *
  LockID(DB
  DB=/test/mail/test.nsf)) Waiters countNonIntentLocks = 1
  
  countIntentLocks = 2, queuLength =
  8
  [1130512:00073-17734]    Req(Status=Granted Mode=S Class=Manual
  
  Nest=0
  Cnt=1
  
  
         Tran=0 Func=N/A
  [1237186:00002-00001])
  [1130512:00073-17734]    Req(Status=Waiting Mode=SIX
  Class=Manual
  Nest=0
  Cnt=1
  
  
         Tran=0 Func=N/A  [1130512:00241-08996]
  Delay=23min)
  [1130512:00073-17734]    Req(Status=Converting Mode=IS
  CnvMode=S
  Class=Manual Nest=0
  Cnt=0(Hold)
         Tran=0 Func=N/A  [1130512:00072-17477]
  Delay=23min)
  [1130512:00073-17734]    Req(Status=Converting Mode=IS
  CnvMode=SIX
  Class=Manual Nest=0
  Cnt=1
         Tran=0 Func=N/A  [1523960:00002-00001]
  Delay=18min)
  [1130512:00073-17734]    Req(Status=Waiting Mode=S Class=Manual
  
  Nest=0
  Cnt=1
  
  
         Tran=0 Func=N/A  [1130512:00315-04627]
  Delay=18min)
  [1130512:00073-17734]    Req(Status=Waiting Mode=S Class=Manual
  
  Nest=0
  Cnt=1
  
  
         Tran=0 Func=N/A  [1269928:00024-05398]
  Delay=16min)
  [1130512:00073-17734]    Req(Status=Waiting Mode=S Class=Manual
  
  Nest=0
  Cnt=1
  
  
         Tran=0 Func=N/A  [1130512:00722-06169]
  Delay=12min)
  [1130512:00073-17734]    Req(Status=Waiting Mode=S Class=Manual
  
  Nest=0
  Cnt=1
  
  
         Tran=0 Func=N/A  [1130512:00267-07968]
  Delay=6min)
  [1130512:00073-17734]    Req(Status=Waiting Mode=S Class=Manual
  
  Nest=0
  Cnt=1
  
  
         Tran=0 Func=N/A  [1130512:00613-03856]
  Delay=0min)
  [1130512:00073-17734] LkMgr END Long Held Lock Dump
  -----------------
  

Local fix

• unknown it was suspected that there was corruption within the
  database and thus
  maintenance was suggested
  

Problem summary

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# VPRS85LKXL.
  This spr is being closed due to no more maintenance releases
   for 7x.  If this issue persists in a later releases (8.5.1 or
   above) it may be re-raised for investigation.
  

APAR Information

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

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

Modules/Macros

• NA
  

Fix information

Applicable component levels

• R704 PSN

     UP