[
https://issues.apache.org/jira/browse/FALCON-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121003#comment-14121003
]
Srikanth Sundarrajan commented on FALCON-644:
---------------------------------------------
{quote}
This could be bad and could result in duplicates. JMS czars, please chime in
here. Why don't we peek into a message, process it, and then remove it upon
completion. Is this possible? This is a good solution IMO. Also, can this be a
separate jira? I'd like to get this committed so there is no correctness issue.
{quote}
I guess it should be possible to create durable subscriber, enable session with
client_ack and ack message when processing is complete. Handle redelivery
appropriately.
> 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)
