A Domino server configured to run with the add-in task NBES.EXE may crash on that task due to excessive memory usage if the server is a member of a Domino cluster and has Streaming Cluster Replication enabled (default).

The root cause of this problem is also documented in Tech Note 1306074.

An example of a crash on the NBES task when it encounters this problem is seen here:

############################################################
### thread 41/86: [ nBES: 0c7c: 0558] FATAL THREAD (Panic)
### FP=0f5da8d0, PC=7c82860c, SP=0f5da860
### stkbase=0f5e0000, total stksize=36864, used stksize=22432
### EAX=0x1129a7c0, EBX=0x77e42014, ECX=0x0f5da7e4, EDX=0x0f5dacfc
### ESI=0x00000d50, EDI=0x00000000, CS=0x0000001b, SS=0x00000023
### DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00000293
############################################################


@[ 8] 0x6017aca8 nnotes.Panic
@[ 9] 0x6017ad2c nnotes.Halt
@[10] 0x60103e95 nnotes.AccessAllProtected
@[11] 0x600469fe nnotes.AccessAll
@[12] 0x60002088 nnotes.DPoolAlloc
@[13] 0x6000441d nnotes.AllocObject
@[14] 0x60006aba nnotes.OSMemAllocExtended
@[15] 0x600071a7 nnotes.OSMemAlloc
@[16] 0x607c7a39 nnotes.NoteUpdateImpl
@[17] 0x607cda5e nnotes.iNoteUpdate2
@[18] 0x607d6efc nnotes.DispatchNoteUpdate
@[19] 0x607d7868 nnotes.NSFNoteUpdateExtended3
@[20] 0x60129f5b nnotes.NSFNoteUpdate
@[21] 0x006695af nBES.RIM_NSFNoteUpdate
@[22] 0x0060c899 nBES.UserOutbox::AddMessage
@[23] 0x008c4498 nBES.`string'


As with the crash on native Domino tasks, thousands of in-memory documents are opened causing Domino shared memory to reach the limit and crash. This problem is more likely to occur on larger clusters (more member servers) and under peak activity. Once an accumulation of document updates occurs, the server may continue to crash until Streaming Cluster Replication is disabled or the fix for SPR JPAI75VH2A is applied.