You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jonathan Anstey (JIRA)" <ji...@apache.org> on 2015/07/23 19:59:04 UTC

[jira] [Resolved] (CAMEL-9003) Allow multiple producers with differing request timeouts

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

Jonathan Anstey resolved CAMEL-9003.
------------------------------------
    Resolution: Fixed

> Allow multiple producers with differing request timeouts
> --------------------------------------------------------
>
>                 Key: CAMEL-9003
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9003
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-netty, camel-netty4
>            Reporter: Jonathan Anstey
>            Assignee: Jonathan Anstey
>             Fix For: 2.16.0, 2.15.3
>
>
> User reported that Camel is 'caching' the timeout setting on outgoing netty calls, so the first call out it would be using the correct timeout setting, but subsequent outgoing calls with different timeout settings Camel would still use the same initial timeout given instead of the new one.
> So usually you would override these kind of things in headers for each request... but you can't just change the timeout value for each call in netty, you'd have to reconstruct the entire channel pipeline... which would be a bit expensive :-) 
> Solution is to add requestTimeout to key for ProducerCache so we get distinct producers with different requestTimeout values.



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