[
https://issues.apache.org/jira/browse/FALCON-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118889#comment-14118889
]
Venkatesh Seetharam commented on FALCON-644:
--------------------------------------------
bq. While we are at it can you also please fix the same in JMSMessageConsumer
This is the client side and we should catch it. Else, they would result in
thread death?
bq. On prod, we have seen instances where post-processing failed because of
activemq issues. Don't know what we are missing
You MUST be running OLD code. :-)
> 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.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)
