[
https://issues.apache.org/jira/browse/OOZIE-2117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Akshay Dange updated OOZIE-2117:
--------------------------------
Description:
We get job failure while sending email notification when we have any xml
reserved strings in our error message .
This can be easily reproduced by running code which will have xml tag in its
error message .
Example to throw an exception with error message:
{code}
if (0 == 0) {
throw new RuntimeException("I have xml tag <someTag>");
}
{code}
Issue at line:
{code}
${wf:errorMessage(wf:lastErrorNode())}
{code}
Error:
{code}
JDOMParseException: Error on line 36: The element type \"someTag\" must be
terminated by the matching end-tag \"</someTag>\".
{code}
Workflow job failure syntax:
{code}
<!-- Email on Failure-->
<action name="fail">
<email xmlns="uri:oozie:email-action:0.1">
<to>${toEmailList}</to>
<subject>Oozie FAILURE in Example- Workflow: ${wf:name()}</subject>
<body>${wf:name()}, ${wf:id()} failed, error
message[${wf:errorMessage(wf:lastErrorNode())}].</body>
</email>
<ok to="kill-fail" />
<error to="kill-fail" />
</action>
<kill name="kill-fail">
<message>${wf:name()} failed, error
message[${wf:errorMessage(wf:lastErrorNode())}]</message>
</kill>
{code}
Issue observed at => Oozie client build version: 3.3.2-cdh4.6.0
was:
We get job failure while sending email notification when we have any xml
reserved strings in our error message .
This can be easily reproduced by running code which will have xml tag in its
error message .
Example to throw an exception with error message:
{code}
if (0 == 0) {
throw new RuntimeException("I have xml tag <someTag>");
}
{code}
Issue at line:
{code}
${wf:errorMessage(wf:lastErrorNode())}
{code}
Error:
{code}
JDOMParseException: Error on line 36: The element type \"someTag\" must be
terminated by the matching end-tag \"</someTag>\".
{code}
Workflow job failure syntax:
{code}
<!-- Email on Failure-->
<action name="fail">
<email xmlns="uri:oozie:email-action:0.1">
<to>${toEmailList}</to>
<subject>Oozie FAILURE in Example- Workflow: ${wf:name()}</subject>
<body>${wf:name()}, ${wf:id()} failed, error
message[${wf:errorMessage(wf:lastErrorNode())}].</body>
</email>
<ok to="kill-fail" />
<error to="kill-fail" />
</action>
<kill name="kill-fail">
<message>${wf:name()} failed, error
message[${wf:errorMessage(wf:lastErrorNode())}]</message>
</kill>
{code}
> wf:errorMessage JDOMParseException
> -----------------------------------
>
> Key: OOZIE-2117
> URL: https://issues.apache.org/jira/browse/OOZIE-2117
> Project: Oozie
> Issue Type: Bug
> Components: workflow
> Affects Versions: 3.3.2
> Reporter: Akshay Dange
>
> We get job failure while sending email notification when we have any xml
> reserved strings in our error message .
> This can be easily reproduced by running code which will have xml tag in its
> error message .
> Example to throw an exception with error message:
> {code}
> if (0 == 0) {
> throw new RuntimeException("I have xml tag <someTag>");
> }
> {code}
> Issue at line:
> {code}
> ${wf:errorMessage(wf:lastErrorNode())}
> {code}
> Error:
> {code}
> JDOMParseException: Error on line 36: The element type \"someTag\" must be
> terminated by the matching end-tag \"</someTag>\".
> {code}
> Workflow job failure syntax:
> {code}
> <!-- Email on Failure-->
> <action name="fail">
> <email xmlns="uri:oozie:email-action:0.1">
> <to>${toEmailList}</to>
> <subject>Oozie FAILURE in Example- Workflow: ${wf:name()}</subject>
> <body>${wf:name()}, ${wf:id()} failed, error
> message[${wf:errorMessage(wf:lastErrorNode())}].</body>
> </email>
> <ok to="kill-fail" />
> <error to="kill-fail" />
> </action>
> <kill name="kill-fail">
> <message>${wf:name()} failed, error
> message[${wf:errorMessage(wf:lastErrorNode())}]</message>
> </kill>
> {code}
> Issue observed at => Oozie client build version: 3.3.2-cdh4.6.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
