camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Cosentino (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CAMEL-8598) Set default timeouts on workflows registered by the camel-aws / aws-swf component
Date Tue, 04 Aug 2015 09:46:04 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-8598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrea Cosentino reassigned CAMEL-8598:
---------------------------------------

    Assignee: Andrea Cosentino

> Set default timeouts on workflows registered by the camel-aws / aws-swf component
> ---------------------------------------------------------------------------------
>
>                 Key: CAMEL-8598
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8598
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-aws
>    Affects Versions: 2.14.2
>            Reporter: Derek Abdine
>            Assignee: Andrea Cosentino
>            Priority: Minor
>             Fix For: 2.16.0
>
>
> The aws-swf component does not set a default "Execution Start To Close Timeout" or "Task
Start To Close Timeout" when workflows are newly registered. 
> This has the effect of scheduled workflows immediately moving to the TIMEOUT state (and
being tracked as timed out in the AWS SWF UI).
> *workarounds*
> For newcomers to the aws-swf component this is particularly confusing. My work-around
was to explicitly create the workflow type in the AWS SWF UI before camel had a chance to
register it with proper timeouts (the UI requires you to set a timeout, which may mean there's
also a bug in the AWS API). Another approach looks to be related to the workflowTypeRegistrationOptions
uri option on the aws-swf endpoint, though I haven't validated that approach as a work-around
for this issue, so explore at your own risk.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message