Potential hang while upgrading the BlackBerry Enterprise Server on IBM Lotus Domino to 5.0.3
While upgrading the BlackBerry Enterprise Server (BES) on IBM Lotus Domino to 5.0.3, be aware of a potential problem that may cause mail servers to hang. Mail servers at risk are those that interact with BES 5.0.3.
The potential hang is triggered based on a specific interaction between the BES and the mail server to process unread marks for BlackBerry enabled users. During this process the BES passes over a list of NoteIDs to the mail server. If the size of this list is greater than 10K and the mail server interacting with the BES has transaction logging enabled, the mail server can experience a hang. Its difficult to predict if any one list would be greater than 10K of unread messages. To be conservative, any environment with larger mail files and transaction logging enabled should request this fix.
Secondary issues that may show up are deadlocks involving semaphores and server crashes. However, the primary indicator for this issue is the hang. No hang will be experienced on the BES Domino server itself.
It is triggered by new code put in to BESD 5.0.3 to better handle read/unread mark synchronization on the BlackBerry during Domino mail server failover as outlined in DT511330. For more information on DT511330, please see the following BlackBerry Knowledge Base document:
Read or unread status changes when failover occurs (KB21083)
This issue will happen with BES Domino version 5.0.3 and above with any version of Domino mail server 6.0 and above.
Diagnosing the problem
How to identify the issue: Take an NSD on the mail server when the hang or deadlock appears. While analyzing the NSD it should match the beginning part of the stack you see below:
@ 0x01cc5200 nnotes.iNSFDbGetMultNoteInfo+348 (1894f098,1894d3fa,3ad0480,b7) @wrap1.c(265)
@ 0x01c6b11d nnotes.NSFDbGetMultNoteInfo+845 (2c0,1d3fa,18940480,b7) @nsfsem2.c(255)
@ 0x10102cc8 nserverl.ServerGetMultNoteInfo+1036 (c698000b,f7600009,0,1894f7e0) @svgninfo.c(142)
@ 0x1005341e nserverl.DbServer+8490 (fc4300ca,c698000b,8bf534a0,4) @dbserver.c(895)
@ 0x1008f854 nserverl.WorkThreadTask+5756 (fbfa000a,0,1,1894fe58) @workthrd.c(547)
@ 0x10002480 nserverl.Scheduler+2104 (0,8128,0,0) @sched.c(322)
As you see above, the beginning part of the NSD should indicate a client is using the NSFDbGetMultNoteInfo call in conjunction with the mail server being in a hung state.
Resolving the problem
This issue is now fixed in Lotus Notes and Domino 8.5.2 FP2 and 8.5.3. The mail servers which interact with the BES must be upgraded. The BES server does not need to be upgraded.
Fix details: SPR# JPAI8E4NTW
Refer to the Upgrade Central site for details on upgrading Notes/Domino.
If you have not yet upgraded, disable read/unread mark synchronization for the BES (both active and standby if utilizing HA configuration) with the following registry key.
On the BlackBerry Enterprise Server, browse to HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Agents\. Create the DWORD value UnreadMarksDisabled.
Enter a value 1 to prevent read/unread message status functionality. Enter a value of 0 to enable this functionality.
More support for:
Software version: 6.0, 7.0, 8.0, 8.5
Operating system(s): AIX, IBM i, Linux, Solaris, Windows, z/OS
Reference #: 1470828
Modified date: 19 October 2011
Translate this page: