You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Venkateswara Rao Desu (JIRA)" <ji...@apache.org> on 2016/08/12 06:27:20 UTC

[jira] [Created] (CAMEL-10242) Enhance Camel to support idleTimeout to avoid network resource wastage due to leak in caller code

Venkateswara Rao Desu created CAMEL-10242:
---------------------------------------------

             Summary: 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


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)