[
https://issues.apache.org/jira/browse/CAMEL-10242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15426193#comment-15426193
]
Venkateswara Rao Desu commented on CAMEL-10242:
-----------------------------------------------
Hi [~hqstevenson],
The solution make sense. As producer would already have handle and generally
close session once done with task. By having this enabled for consumer, we
could save lot of servers which hold lot of open sockets without being used.
> camel-mllp - Enhance Camel to support idleTimeout to avoid network resource
> wastage due to leak in caller code
> --------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-10242
> URL: https://issues.apache.org/jira/browse/CAMEL-10242
> Project: Camel
> Issue Type: Improvement
> Components: camel-mllp
> Affects Versions: 2.17.3
> Reporter: Venkateswara Rao Desu
> Assignee: Quinn Stevenson
> Fix For: Future
>
>
> For a good client and Server , idle timeout is not required.
> But when client has bugs which open socket but not close, then server would
> have ESTABLISHED connections pilled up. Which end up restarting the process
> or killing sockets manually.
> To avoid this we should have idleTimeout for all mllp connections.
> This is in reference to :
> https://github.com/hqstevenson/camel-mllp/issues/14#issuecomment-238911254
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
