Notes/Domino Fix List
 |  |
| SPR # SKAI6J58UL | Fixed in 6.5.6; 7.0.2; 6.5.5 FP2 release | Regression in 6.5.4 |
Product Area: Server Technical Area: Sametime Platform: Cross Platform
Lotus Customer Support APAR: LO11144
SPR# SKAI6J58UL - Fixed a Domino server hang with 0x0244 database semaphore when the cleanup thread was loaded. Prior to this fix, there was a timing issue with the creation of the osfdg shutdown thread and the process shutdown which can result in a loss of an the OSCreateThread event and thus block any thread creation from then on.
Technote Number: 1248297
Problem:
This issue was reported to Quality Engineering as SPR# SKAI6J58UL, and is fixed
in the following releases:
Domino 6.5.5 Fix Pack 2 (FP2)
Domino 6.5.6
Domino 7.0.2
Excerpt from the Lotus Domino 6.5.5, 6.5.6,and 7.0.2 fix lists (available at
http://www.ibm.com/developerworks/lotus):
Sametime
SPR# SKAI6J58UL - Fixed a Domino server hang with 0x0244 database semaphore
when the cleanup thread was loaded. Prior to this fix, there was a timing issue
with the creation of the osfdg shutdown thread and the process shutdown which
can result in a loss of an the OSCreateThread event and thus block any thread
creation from then on.
There is no workaround for this issue.
Supporting Information:
This problem causes a server thread to stall inside OSWaitEvent as it sits
waiting forever for a thread to be generated. While stuck in this state all
other threads attempting to do the same activity as the first need to queue
behind it ,thus causing the hang symptom. The stack looks like this (on W32):
############################################################
### thread 29/79: [ nserver: 08b0: 0eb4]
### FP=07a8ed98, PC=77f82870, SP=07a8ed74
### stkbase=07a90000, total stksize=262144, used stksize=4748
############################################################
@[ 1] 0x77f82870 ntdll.NtWaitForSingleObject+11
(49c,ffffffff,0,600a9077)
@[ 2] 0x7c57b3db KERNEL32.WaitForSingleObject+15 (9,0,60c71dc4,0)
@[ 3] 0x600d726d nnotes._OSWaitEvent@8+29 (10d26aa,0)
@[ 4] 0x60116dce nnotes._OSCreateThread@16+46
(608f5ee0,40000,518149f0,0)
@[ 5] 0x608f5d4b nnotes._NAMELookupAcquireThread@12+443
(7a8ee4c,0,831405)
@[ 6] 0x608ec578 nnotes._ThreadedNAMELookup@48+24
(0,8206,0,0,0,1,0,0,0,0,0,0)
@[ 7] 0x600acc08 nnotes._NAMELookup2@36+264
(0,8006,1,60a60b8c,0,1,0,0,0)
@[ 8] 0x60344f86 nnotes._SECLookup2@40+70 (7a8f246,0,8006,1,0,1,0,0,0,0)
@[ 9] 0x60344444 nnotes._SecSearchForEntry@12+116 (7a8f23c,0,2)
@[10] 0x60344377 nnotes._SecSearchAndCheckEntry@12+23 (7a8f23c,0,2)
@[11] 0x60344310 nnotes._SecSearchDirectories@8+64 (7a8f23c,0)
@[12] 0x60344254 nnotes._SecSearchNameSpaces@4+148 (1)
@[13] 0x60344021 nnotes._FindAddressBookEntry@44+369
(0,2,7a8f304,7a8f310,0,1,0,0,0,0,0)
@[14] 0x60343e7a nnotes._SECFindAddressBookEntry@40+122
(0,1,7a8f304,7a8f310,0,1,0,0,0,0)
@[15] 0x6090d773 nnotes._LookupNameInfo@112+163 (2,7a8f73c,1d,460b755c)
@[16] 0x6090d3fe nnotes._LookupABPIandKeys@112+270
(2,7a8f73c,1d,460b755c)
@[17] 0x6090d2e4 nnotes._FindABPIandKeys@112+212
(7a8f73c,1d,460b755c,86)
@[18] 0x6090cfac nnotes._CheckABPublicInfo@112+268
(0,7a8f874,7a8f73c,1d)
@[19] 0x6014b7eb nnotes._LookupABPI@8+651 (fde4,0)
@[20] 0x6014b1bf nnotes._Parse_DistName@8+143 (7a8fde4,1)
@[21] 0x60913622 nnotes._AuthServerDialog@12+2178 (48846f6e,1,0)
@[22] 0x600d2e85 nnotes._AuthStateMachine@4+213 (7a8fde4)
@[23] 0x60904bfa nnotes._AUTHProcessNetbfr@12+186
(de300052,1001ef10,7a8fea8)
@[24] 0x1001a310 nserverl._DbServer@8+1264 (db0486,11d800a6)
@[25] 0x1002de4d nserverl._WorkThreadTask@8+1597 (4d34288,0)
@[26] 0x100016cb nserverl._Scheduler@4+763 (0)
@[27] 0x60116d74 nnotes._ThreadWrapper@4+212 (0)
@[28] 0x7c57b388 KERNEL32.lstrcmpiW+183 (0,0,0,0) More >
Last Modified on 12/10/2013
Go back
|