How undestand NSD?

Guys,

How can I identify what is the database that is freezing the server? How can I find the database table [nSERVER:06b0: 58] ?

NSD Below

############################################################

FATAL THREAD 56/79 [ nSERVER:06b0: 2316]

FP=0x0748f85c, PC=0x6018f8e3, SP=0x0748eee4, stksize=2424

EAX=0x00d5088c, EBX=0x00000000, ECX=0x00820000, EDX=0x00820000

ESI=0x0748f4f0, EDI=0x0748f8b8, CS=0x0000001b, SS=0x00000023

DS=0x00000023, ES=0x00000023, FS=0x0000003b, GS=0x00000000 Flags=0x00010202

Exception code: c0000005 (ACCESS_VIOLATION)

############################################################

PASS 2 : FATAL THREAD with STACK FRAMES 56/79 [ nSERVER:06b0: 2316]

FP=0748f85c, PC=6018f8e3, SP=0748eee4, stksize=2424

Exception code: c0000005 (ACCESS_VIOLATION)

[ nSERVER:06b0: 2316] [ nSERVER:06b0: 358] [ nSERVER:06b0: 58]

Regards

Subject: how undestand NSD?

You’ve found the fatal thread - now search for the TID (“06b0: 2316” in this case).

You should find a table that maps this to a virtual ID.

Search for that ID and you’ll find the open files for the thread.

nServer crashing probably means that the db(s) in question are damaged.

Subject: how undestand NSD?

The only time I have ever seen Domino crash constantly without the cause of LotusScript, was that a database had a huge number of huge attachments in one document. Putting the attachments on seperate documents solved the problem. The reason why it crashed, was that the server ran out of memory when trying to open that document with all the attachments.