Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
Unknown
Description
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.