Answered by:
Unhandled Exceptions

Question
-
If an application that is being run by the Job Manager throws an unhandled exception, the job will continue to keep running indefinitely. If the application running in a task generates an unhandled exception the just-in-time debugger dialog comes up on the node where the task was running and the job remains in a running state. The only way to get the job to fail is to login to the nodes and close the dialog box, which in turn causes the job to fail. Is there any way to make the jobs fail without interaction with the node if an exception is thrown?
- Moved by Rae WangModerator Thursday, June 18, 2009 12:21 AM (From:Windows HPC Server Deployment, Management, and Administration)
Tuesday, June 16, 2009 12:30 PM
Answers
-
The JIT debugger should be disabled for a production cluster. See http://msdn.microsoft.com/en-us/library/k8kf6y2a.aspx
Thanks, Colin
-Colin Microsoft HPC- Proposed as answer by Josh BarnardModerator Friday, June 19, 2009 8:08 PM
- Marked as answer by Don PatteeModerator Tuesday, August 11, 2009 1:14 AM
Friday, June 19, 2009 1:16 AMModerator -
You could also try setting the registry key directly on your compute nodes. See http://msdn.microsoft.com/en-us/library/5hs4b7a6(VS.80).aspx for the details.
Regards,
Robert- Proposed as answer by Josh BarnardModerator Thursday, July 30, 2009 7:01 PM
- Marked as answer by Don PatteeModerator Tuesday, August 11, 2009 1:14 AM
Thursday, July 30, 2009 6:55 PM
All replies
-
The JIT debugger should be disabled for a production cluster. See http://msdn.microsoft.com/en-us/library/k8kf6y2a.aspx
Thanks, Colin
-Colin Microsoft HPC- Proposed as answer by Josh BarnardModerator Friday, June 19, 2009 8:08 PM
- Marked as answer by Don PatteeModerator Tuesday, August 11, 2009 1:14 AM
Friday, June 19, 2009 1:16 AMModerator -
The only option I have available with regards to Visual Studio is the Visual Studio 2005 remote Debugger which doesn't give you the option to turn off. Should this be removed?
Monday, June 22, 2009 5:34 PM -
You could also try setting the registry key directly on your compute nodes. See http://msdn.microsoft.com/en-us/library/5hs4b7a6(VS.80).aspx for the details.
Regards,
Robert- Proposed as answer by Josh BarnardModerator Thursday, July 30, 2009 7:01 PM
- Marked as answer by Don PatteeModerator Tuesday, August 11, 2009 1:14 AM
Thursday, July 30, 2009 6:55 PM