Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Thu, 20 Sep 2012 07:23:08 +1100 (NCT)
From: =?utf-8?Q?Christian_M=C3=BCller_=28JIRA=29?= <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <1336011989.99240.1348086188555.JavaMail.jiratomcat@arcas>
In-Reply-To: <1330837527.76817.1341173632554.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Closed] (CAMEL-5414) SqsEndpoint can't retrieve existing
 queue url with visibility timeout different than default
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/CAMEL-5414?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian M=C3=BCller closed CAMEL-5414.
-----------------------------------

    Resolution: Fixed

I updated the behavior as discussed.
               =20
> SqsEndpoint can't retrieve existing queue url with visibility timeout dif=
ferent than default
> -------------------------------------------------------------------------=
-------------------
>
>                 Key: CAMEL-5414
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5414
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-aws
>    Affects Versions: 2.9.2
>            Reporter: Luc Pezet
>            Assignee: Christian M=C3=BCller
>             Fix For: 2.9.4, 2.11.0, 2.10.2
>
>         Attachments: SqsEndpointTest.java
>
>
> This would happen in 2 scenarios:
> 1. Queue already exists with vsibility timeout different than 30 seconds =
(say use AWS Console to create a queue and set a different visibility timeo=
ut). Using this queue as an endpoint and problem will occur
> 2. Queue DOES NOT already exist and is created by SqsEndpoint (createQueu=
e). If "defaultVisibilityTimeout" configured, it will still work...the firs=
t time. But restarting the endpoint (or the whole camel app) and the proble=
m will occur.

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