Yes, you need to add a signalhandler to your STAX job definition. For example, here was mine:
<signalhandler signal="'STAXPythonEvaluationError'">
<sequence>
<log level="'error'">"STAXPythonEvaluationError\n\n%s" %
STAXPythonEvalMsg</log>
<log level="'trace'">"Try using methods like pprint.pprint
(anObject) for printing out objects that you think should be here.\nYou can
also use Python to set variables that perhaps caused this error."</log>
<log level="'trace'">"\n".join(dir())</log>
<log level="'trace'">"E-MAILING %s" % emailAddress</log>
<import machine="'local'" file="emailManager" />
<call function="'notifyPythonEvaluationError'">staxMachine
[0], STAXJobID, emailAddress, 1, STAXPythonEvalMsg.replace
("\n","<br />")</call>
<!-- keep this log message. it lets any potential parent
job know that the job was terminated (or held) due to a python error ... IF
this is the last user log in the log stack thing. -->
<log level="'error'">"STAXPythonEvaluationError Terminated
Job"</log>
<!-- change this to a hold statement if you want it to hold
instead of terminate. -->
<!-- <hold />-->
<terminate block="'main'" />
</sequence>
</signalhandler>
- Paul
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Luca Robusto <lucarobu...@gmail.com>
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|STAF-USERS-REQUESTS <staf-users@lists.sourceforge.net>,
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|05/03/2013 10:54 AM
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|[staf-users] python error execution without terminating Job
|
>--------------------------------------------------------------------------------------------------------------------------------------------------|
Is it possible not to termine a Job in Stax when a python error occurs
(E.g. not declared or initialized variables) ?
Luca.
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
staf-users mailing list
staf-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/staf-users
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________ staf-users mailing list staf-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/staf-users
