[
https://issues.apache.org/jira/browse/CAMEL-10242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468103#comment-15468103
]
ASF GitHub Bot commented on CAMEL-10242:
----------------------------------------
GitHub user hqstevenson opened a pull request:
https://github.com/apache/camel/pull/1159
CAMEL-10242 - add timeout
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hqstevenson/camel CAMEL-10242
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/1159.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1159
----
commit 1fe263c3fc46664b58e4eec2cf099c8e3d7f1707
Author: Quinn Stevenson <[email protected]>
Date: 2016-09-06T18:11:05Z
CAMEL-10242 - added support for connection timeout
commit 164aa417c9bb97e2d258da22091e8d7656346be6
Author: Quinn Stevenson <[email protected]>
Date: 2016-09-06T18:13:45Z
resync CAMEL-10242 with master
----
> 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)
