camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tracy Snell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-5944) Setting extendMessageVisibility on an SQS consumer doesn't make visibilityTimeout compulsory
Date Sun, 13 Jan 2013 16:28:12 GMT

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

Tracy Snell commented on CAMEL-5944:
------------------------------------

Added a note in the documentation.
                
> 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
>            Assignee: Tracy Snell
>            Priority: Minor
>         Attachments: CAMEL-5944-clean.patch
>
>
> 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

Mime
View raw message