You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Phil Cluff (JIRA)" <ji...@apache.org> on 2013/01/10 01:10:12 UTC

[jira] [Commented] (CAMEL-5944) Setting extendMessageVisibility on an SQS consumer doesn't make visibilityTimeout compulsory

    [ https://issues.apache.org/jira/browse/CAMEL-5944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13549216#comment-13549216 ] 

Phil Cluff commented on CAMEL-5944:
-----------------------------------

Implementation and tests on my Github fork: https://github.com/GeneticGenesis/camel/tree/camel-2.10.x-CAMEL-5944-extendMessageVisibility-requires-visibilityTimeout
                
> Setting extendMessageVisibility on an SQS consumer doesn't make visibilityTimeout compulsory
> --------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-5944
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5944
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-aws
>    Affects Versions: 2.10.3
>            Reporter: Phil Cluff
>            Priority: Minor
>
> The ExtendMessageVisibility functionality in SQS Consumer doesn't work unless visibilityTimeout is set (SqsConsumer.java L110), but the documentation doesn't sugggest this, and it isn't enforced.
> I'd suggest that we change the config/documentation such that visibilityTimeout becomes compulsory if extendMessageVisibility is set.
> Another option may be to check for available timeouts in the following order:
> 1) visibilityTimeout
> 2) defaultVisibilityTimeout
> 3) Fall back to a default value (30s?). [In this case, it would probably be sensible to log warning that we were using a default value.]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira