[
https://issues.apache.org/jira/browse/FALCON-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119390#comment-14119390
]
Shwetha G S commented on FALCON-644:
------------------------------------
{quote}
While we are at it can you also please fix the same in JMSMessageConsumer
{quote}
Can we add the message back to the queue(helps in case of temporary failures
like connection issues, but also have to handle starvation) and log in an alert
file which can be monitored?
{quote}
On prod, we have seen instances where post-processing failed because of
activemq issues. Don't know what we are missing
{quote}
As you pointed out, this code hasn't changed since the beginning. So, nothing
to do with running old code. [~shaik.idris] pointed out that the issues were
because of activemq connection issues and the jobs were stuck. If I come across
any new ones, will check
> Falcon message producer masks errors in Post processing
> -------------------------------------------------------
>
> Key: FALCON-644
> URL: https://issues.apache.org/jira/browse/FALCON-644
> Project: Falcon
> Issue Type: Bug
> Components: messaging
> Affects Versions: 0.6
> Reporter: Sowmya Ramesh
> Assignee: Venkatesh Seetharam
> Priority: Blocker
> Fix For: 0.6
>
> Attachments: FALCON-644-v1.patch, FALCON-644.patch
>
>
> In JMSMessageProducer all the exceptions are caught and success is returned
> [return 0] by default. Oozie will indicate that this WF action was successful
> as Falcon Messaging returns success.
> WF shouldn't be failed if post-processing fails but instead of masking errors
> this can be controlled in the WF decision on failure.
> {noformat}
> <action name='succeeded-post-processing'>
> ...
> <ok to="end"/>
> <!-- Shouldn't fail the WF if post processing fails -->
> <error to="end"/>
> </action>
> {noformat}
> Thoughts?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
