[
https://issues.apache.org/jira/browse/CAMEL-8598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380956#comment-15380956
]
ASF GitHub Bot commented on CAMEL-8598:
---------------------------------------
GitHub user ssharma opened a pull request:
https://github.com/apache/camel/pull/1079
https://issues.apache.org/jira/browse/CAMEL-8598
The defaults as part of above bug are not used by AWS client before
starting a workflow
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ssharma/camel master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1079.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1079
----
commit 9536bf91862324532aea88bf33793720c36e843e
Author: siddharth.sharma <[email protected]>
Date: 2016-07-16T21:18:52Z
https://issues.apache.org/jira/browse/CAMEL-8598
The defaults as part of above bug are not used by AWS client before
starting a workflow
----
> 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.15.3, 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)
