camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-9003) Allow multiple producers with differing request timeouts
Date Thu, 23 Jul 2015 12:56:04 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-9003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638756#comment-14638756
] 

Claus Ibsen commented on CAMEL-9003:
------------------------------------

People should really be careful, if you have 1000s of different timeout values you have 10000s
of different producers. This is bad.

People should maybe settle for a limited number of different timeouts and use that only.

> 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)

Mime
View raw message