Repeated crash protection

When certain Notes® documents are corrupted or contain non-standard content, they can cause the IBM Traveler server to repeatedly crash as it tries to process these documents. A repeating crash prevention feature exists to help minimize IBM Traveler server outage in these instances.

This feature was first introduced in version 8.5.2.3. It detects a repeat crash scenario for a particular document, then bans the document from being processed by the server. The document remains banned permanently unless cleared by an Administrator. The server then starts and runs normally. The only impact to the end user is that the banned document does not sync to the mobile device.

Settings

By default, the repeated crash protection is enabled and set to detect and ban a document after the sixth crash. The number of crashes before banning a document can be configured by changing parameters in the notes.ini file. Both of these parameters are dynamic and can be set using the Domino® set config command.

NTS_BANNED_DOC_LIMIT=5

A setting of 0 disables crash protection.

NTS_BANNED_DOC_SYNCS=3

This sets the number of device syncs on where the crash protection code is running when a user connects to a specific IBM Traveler server. A setting of 0 will disable crash protection.

Administration

To administer the banned documents, the following additional Tell commands have been added to the IBM Traveler server.

Table 1. Additional Tell commands
Command	Description
Tell Traveler BannedDoc show DocID UserID	Shows the specified banned document. DocID is the UNID or a noteID of a document.
Tell Traveler BannedDoc show * UserID	Lists all of the banned documents for the specified user. Any candidate (to ban) documents are also listed. A candidate means that a crash has occurred while the document was open and is now being tracked for potential banning.
Tell Traveler BannedDoc show *	Lists all of the banned documents on the system. Any candidate documents to ban are also listed. This content is also included in the systemdump output.
Tell Traveler BannedDoc Remove DocID UserID	Removes the ban for a particular document. DocID is the UNID or a noteID of a document.
Tell Traveler BannedDoc Remove * UserID	Removes the ban for all banned documents for the specified user.
Tell Traveler BannedDoc Remove *	Removes the ban for all banned documents on the server.
Tell Traveler BannedDoc Add DocID UserID	Bans a particular document from syncing. DocID is the UNID or a noteID of a document.
Tell Traveler BannedDoc dump	Attempts to dump all of the banned documents to `DumpDoc.nsf`. This should only be used if providing IBM® support the documents in question for troubleshooting purposes.