LO48209: ROUTER HUNG ON WITH LOGGER APPEND SEMAPHORE TIMEOUTS.

APAR status

• Closed as fixed if next.

Error description

• The majority of the semaphore timeouts were for the router
  thread 245852:07968
  which appears to have contributed to the bottleneck.
  It appears that the thread was attempting to deliver a message,
  followed by an
  attempt to write to the transaction log.
  
  Another observation was that in the console log seconds later
  there appeared
  lkmgr timeouts which are equivalent to semaphore timeouts.
  Most of those holding threads were also waiting for
  245852:07968:
  [122916:00002-00001] 01/25/2010 14:31:23
  [196800:00146-36238] LkMgr BEGIN Long Held Lock Dump
  ------------------
  [196800:00146-36238] Lock(Mode=SIX* LockID(DB
  DB=/servert/data/mail/test.nsf))
  Waiters countNonIntentLocks = 2 countIntentLocks = 1, queuLength
  = 1
  [196800:00146-36238]    Req(Status=Granted Mode=SIX Class=Manual
  Nest=0 Cnt=2
         Tran=427512947 Func=N/A  [245852:00034-07454])
  dbfolder_c:9275
  [196800:00146-36238]    Req(Status=Converting Mode=IS CnvMode=S
  Class=Manual
  Nest=0 Cnt=0(Hold)
         Tran=0 Func=N/A  [196800:01025-26472] Delay=1min)
  [196800:00146-36238] Lock(Mode=SIX* LockID(DB
  DB=/servert/data/mail3.box))
  Waiters countNonIntentLocks = 1 countIntentLocks = 0, queuLength
  = 8
  [196800:00146-36238]    Req(Status=Granted Mode=SIX Class=Manual
  Nest=-1 Cnt=1
         Tran=0 Func=N/A  [245852:00008-01029])
  [196800:00146-36238]    Req(Status=Waiting Mode=S Class=Manual
  Nest=-1 Cnt=1
         Tran=0 Func=N/A  [196800:01342-07968] Delay=1min)
  
  The following debugs were suggested:
   DebugRouter=3
  Log_mailrouting=40
  debug_rm_debug=1
  
  Also suggested disabling txn on the mail.boxes since daos was
  not running:
  MailBoxDisableTXNLogging=1
  

Local fix

• unknown
  

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# VPRS822ULN.
  The problem will be fixed in the next release of the product.
  

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

• R800 PSN

     UP