[
https://issues.apache.org/jira/browse/CAMEL-10158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Sharma updated CAMEL-10158:
-------------------------------------
Patch Info: Patch Available
Affects Version/s: (was: 2.14.2)
2.17.2
Fix Version/s: (was: 2.15.3)
(was: 2.16.0)
Description:
Need support to tag workflow execution in AWS SWF.
{code}com.amazonaws.services.simpleworkflow.flow.StartWorkflowOptions{code)
supports adding List<String> to any workflow execution.
Enhance *CamelSWFWorkflowClient* to use List<String> from incoming Exchange
headers before starting a workflow execution
was:
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.
> Support to add tags to workflow execution in camel-aws component
> ----------------------------------------------------------------
>
> Key: CAMEL-10158
> URL: https://issues.apache.org/jira/browse/CAMEL-10158
> Project: Camel
> Issue Type: Improvement
> Components: camel-aws
> Affects Versions: 2.17.2
> Reporter: Siddharth Sharma
> Assignee: Andrea Cosentino
> Priority: Minor
>
> Need support to tag workflow execution in AWS SWF.
> {code}com.amazonaws.services.simpleworkflow.flow.StartWorkflowOptions{code)
> supports adding List<String> to any workflow execution.
> Enhance *CamelSWFWorkflowClient* to use List<String> from incoming Exchange
> headers before starting a workflow execution
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
