Risorse per professionisti IT >
Home page del forum
>
Windows HPC Server Job Submission and Scheduling
>
Unhandled Exceptions
Unhandled Exceptions
- 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?
- SpostatoRae WangMSFT, Moderatoregiovedì 18 giugno 2009 0.21 (From:Windows HPC Server Deployment, Management, and Administration)
Risposte
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- Contrassegnato come rispostaDon PatteeMSFT, Moderatoremartedì 11 agosto 2009 1.14
- Proposto come rispostaJosh BarnardMSFT, Proprietariovenerdì 19 giugno 2009 20.08
- 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- Proposto come rispostaJosh BarnardMSFT, Proprietariogiovedì 30 luglio 2009 19.01
- Contrassegnato come rispostaDon PatteeMSFT, Moderatoremartedì 11 agosto 2009 1.14
Tutte le risposte
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- Contrassegnato come rispostaDon PatteeMSFT, Moderatoremartedì 11 agosto 2009 1.14
- Proposto come rispostaJosh BarnardMSFT, Proprietariovenerdì 19 giugno 2009 20.08
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?
- 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- Proposto come rispostaJosh BarnardMSFT, Proprietariogiovedì 30 luglio 2009 19.01
- Contrassegnato come rispostaDon PatteeMSFT, Moderatoremartedì 11 agosto 2009 1.14
