70 | An IBM provided NSD crash file analyzerHans Christian Koch1362 - 12 2008 / (2) IBM should/could provide an application (possible even embedded in the Admin client) that could take an NSD crashfile and parse it; Remove all the irellevant information, find the virtual/physical threads that had crashed, maybe even the NoteID of the document/designelement that caused the crash. Wouldn't that be awsome. Seconds ... |
34 | NSD Kill for specific task or PIDMarie Scott5130 - 14 2008 / (0) There are circumstances when it would be helpful to be able to "kill" or "stop" a specific server task that is not responding to a quit without having to bring the server down entirely. Perhaps an NSD -kill on specific PID so that you can kill a specific task without having ... |
25 | Server NSDs: Send to IBM automatically when createdMike McPoyle397 - 17 2009 / (0) As I was zipping up some NSDs and sending them to IBM from a recent server crash, I wondered how efficient this really was? How many times does a server crash, and it's so rare that the crash is never reported? Creating a PMR isn't difficult, but I'd much rather click an ... |
7 | NSD should collect web server log if logging enabledMark Demicoli10736 - 09 2014 / (0) A HTTP crash could be more easily diagnosed if we knew the URL being fetched when the thread crashed, therefore it is logical to include web server logs (if enabled) in the Fault Report document. |
-2 | Check NSD.exe version on server startupChuck Hauble870 - 11 2007 / (0) Having an incorrect version of NSD.exe on a server can be a nightmare when trying to troubleshoot server crash issues. Could the server process at start up check to see if the correct NSD version is available based on the version of the server code and display a warning if ... |