>> sun.net.client.defaultReadTimeout?
>>>> Yeah timeout setting is actually hard as well.
>>>> You got the OS level, the JVM, the JVM system properties, the
>>>> framework and then Camel as well.
>>>> And they all got different/independent timeout and
Camel. Some of the
>>> transports offer a timeout.
>>> - JMS
>>> - Mina
>>> - and maybe some others but I cannot remember. But its documented in
>>> the wiki if they have a timeout option
>>>
>>> However we could consider having a Ca
er a timeout.
>> - JMS
>> - Mina
>> - and maybe some others but I cannot remember. But its documented in
>> the wiki if they have a timeout option
>>
>> However we could consider having a Camel timeout feature so Camel at
>> least could and indic
amel timeout feature so Camel at
> least could and indicate a timeout error.
> However its not easy to do with all protocols. And we need some latch
> around that can trigger when a timeout occur.
>
> But I do think we could add something to the SendToProcessor that can
> support
ut I do think we could add something to the SendToProcessor that can
support a custom Camel timeout that kinda overrule any other.
But this requires a latch and to use a different thread for sending.
Or am I wrong on this?
Any thought?
>
> Hari Gangadharan
> --
> View this message in conte
://www.nabble.com/Camel-stuck-periodicallly---HTTP-timeout-issue-tp23659334p23659334.html
Sent from the Camel - Users mailing list archive at Nabble.com.
