You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Ashok R S (JIRA)" <ji...@apache.org> on 2016/01/19 21:30:39 UTC

[jira] [Updated] (CAMEL-9525) Camel-Netty unable to send request incase of endpoint failure and connections are in hung state

     [ https://issues.apache.org/jira/browse/CAMEL-9525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ashok R S updated CAMEL-9525:
-----------------------------
    Description: 
Hi Team,

We are using camel netty component (version: 2.11.2) for client to server TCP socket communication in a full duplex mode..

Currently what is happening is, incase our endpoint is down not necessasrily ports are down, the netty is not able to send requests to end point. When we checked the telnet to the endpoints ip and port, it shows connection as established but it is not able to send the requests at all. Also on the server side,, connections appear as established

Ours is full duplex communication. What we need to know is what are the parameters to be set in order to close idle connection and to ensure if the current parameters which we have set will hold good for netty to work as expected.

Our route looks like the below:
<from uri="direct:sourceRoute">
  <inOut uri="netty:tcp://{{ip:port}}?textline=true&sync=true&decoderMaxLineLength={{restMaxLineLength}}&autoAppendDelimiter=false&amp;disconnect=false&producerPoolMaxActive=10&producerPoolMinEvictableIdle=3000" />
                    

  was:
Hi Team,

We are using camel netty component (version: 2.11.2) for client to server TCP socket communication in a full duplex mode..

Currently what is happening is, incase our endpoint is down not necessasrily ports are down, the netty is not able to send requests to end point. When we checked the telnet to the endpoints ip and port, it shows connection as established but it is not able to send the requests at all.

Ours is full dupelx communication. What we need to know is what are the parameters to be set in order to close idle connection and to ensure if the current parameters which we have set will hold good for netty to work as expected.

Our route looks like the below:
<from uri="direct:sourceRoute">
  <inOut uri="netty:tcp://{{ip:port}}?textline=true&sync=true&decoderMaxLineLength={{restMaxLineLength}}&autoAppendDelimiter=false&amp;disconnect=false&producerPoolMaxActive=10&producerPoolMinEvictableIdle=3000" />
                    


> Camel-Netty unable to send request incase of endpoint failure and connections are in hung state
> -----------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-9525
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9525
>             Project: Camel
>          Issue Type: Test
>          Components: camel-netty
>    Affects Versions: 2.11.2
>         Environment: Production, Test environment
>            Reporter: Ashok R S
>
> Hi Team,
> We are using camel netty component (version: 2.11.2) for client to server TCP socket communication in a full duplex mode..
> Currently what is happening is, incase our endpoint is down not necessasrily ports are down, the netty is not able to send requests to end point. When we checked the telnet to the endpoints ip and port, it shows connection as established but it is not able to send the requests at all. Also on the server side,, connections appear as established
> Ours is full duplex communication. What we need to know is what are the parameters to be set in order to close idle connection and to ensure if the current parameters which we have set will hold good for netty to work as expected.
> Our route looks like the below:
> <from uri="direct:sourceRoute">
>   <inOut uri="netty:tcp://{{ip:port}}?textline=true&sync=true&decoderMaxLineLength={{restMaxLineLength}}&autoAppendDelimiter=false&amp;disconnect=false&producerPoolMaxActive=10&producerPoolMinEvictableIdle=3000" />
>                     



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)