[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] regarding tcp connection in ECF
- From: abhisek saikia <agscontact@xxxxxxxxx>
- Date: Sun, 27 Jun 2010 17:44:23 +0530
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=afxJN2FQiRlKLAy5YuWTlVPMy3vAp+TWOJ/pn40Iw7ib5ESbuWsGRM3WJ3LpH65vih O+nN3tKhlmRqxlrVCE8s/OP5X+49Ln6hfHm4Yb6CcW1dZJUcFaR3WhDTLAk85txXkdJN GEjaYfK+wS75STsnoaN/bJwO3O3DGEumcGEP4=
Thanks for sharing this information.I thought the remote service calls will never fail once discovered and added in consumer:) .I want to have this reconnect logic on timeout in my local bundle.Is there any abstraction for ecf generic/jmdns to do so? Could you please give some hints which part of code do i need to modify to serve my purpose.
Thanks and Regards
On Sat, Jun 26, 2010 at 8:28 PM, Scott Lewis <slewis@xxxxxxxxxxxxx>
Yes, you can increase the timeout by changing the container's keepAlive. Of course this has/should be set similarly on both the server and client containers.
abhisek saikia wrote:
Thanks for the information.I didnt know it before.So i can increase the timeout by changing the container id 's keepAlive value
"ecftcp://localhost:3282/server keepAlive=30000" is it correct?
If the keepAlive time is reached (with no traffic) the underlying socket will be disconnected. All subsequent remote service calls will be failed (no connection means no communication :).
So in this case,once the that keepalive time is reached,all my remote services calls will be failed.
You can make the timeout essentially infinite, and then the keep alive will never result in disconnection.
Please correct me if i am wrong.Is there any way to handle this.Is there any way to avoid this timeout so that the remote services will be alive always untill i restart or terminate the equinox.
Of course if disconnection occurs for some other reason, you will have to reconnect.