You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2019/05/19 08:32:00 UTC
[jira] [Updated] (CAMEL-13541) Race condition in camel-hystrix when
xecutionTimeoutInMilliseconds() and onFallback() are used
[ https://issues.apache.org/jira/browse/CAMEL-13541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-13541:
--------------------------------
Fix Version/s: 2.25.0
2.24.1
2.23.3
3.0.0-M3
3.0.0
> Race condition in camel-hystrix when xecutionTimeoutInMilliseconds() and onFallback() are used
> -----------------------------------------------------------------------------------------------
>
> Key: CAMEL-13541
> URL: https://issues.apache.org/jira/browse/CAMEL-13541
> Project: Camel
> Issue Type: Bug
> Components: camel-hystrix
> Affects Versions: 2.18.0
> Reporter: Andrea Tarocchi
> Assignee: Andrea Tarocchi
> Priority: Major
> Fix For: 3.0.0, 3.0.0-M3, 2.23.3, 2.24.1, 2.25.0
>
> Attachments: HystrixTimeoutWithFallbackTest.java
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If e{{xecutionTimeoutInMilliseconds()}} and {{onFallback()}} are used together in a camel hystrix definition. When an Hystrix timeout occurs there might be race conditions in modifying the running exchange between the 2 hystrix threads running in {{HystrixProcessorCommand.run()}} and {{HystrixProcessorCommand.()}}.
> This can be verified running the attached modified {{HystrixTimeoutWithFallbackTest}} test inside {{components/camel-hystrix}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)