Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of hidayath.basha@saventech.com
 designates 216.32.181.183 as permitted sender)
Received-SPF: pass (mail177-ch1: domain of saventech.com designates
 157.56.237.101 as permitted sender) client-ip=157.56.237.101;
 envelope-from=hidayath.basha@saventech.com;
 helo=BY2PRD0810HT005.namprd08.prod.outlook.com ;.outlook.com ;
From: hidayath <hidayath.basha@saventech.com>
To: <users@tomcat.apache.org>
Subject: Connection not Closed at TCP level
Date: Wed, 7 Aug 2013 15:42:15 +0530
Message-ID: <005201ce9356$99cc80f0$cd6582d0$@basha@saventech.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0053_01CE9384.B384BCF0"
Thread-Index: Ac6TVpdPkngaD/uRTAuDwiERG2fhBQ==
Content-Language: en-us

------=_NextPart_000_0053_01CE9384.B384BCF0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

 
We have a websocket application which keeps writing data to the clients. 

 
We found that when tabs (not whole browser) of Firefox (ver. 22) is closed,
the websocket connection is not closed. Anyway, reproducibility is very low.
And the sendQ (netstat -an) keeps growing

 
So, what we did is. we kept sending heart beat from client. If this heart
beat timeout occurs, we are trying to close the connection as follows

ByteBuffer bbuff = ByteBuffer.allocate(1);

bbuff.put((byte) 0);

messageInbound.getWsOutbound().close(0, bbuff);

 
Is this correct approach to close the connection from server? Because, the
connection is not closed at lower level (netstat -an). Anyway, writing data
to it , is stopped and sendQ stops growing.

 
# netstat -an | grep :8080

tcp        0 402376 172.22.59.176:8080      198.162.18.207:64805
ESTABLISHED

 
Thanks and regards,

Hidayath


------=_NextPart_000_0053_01CE9384.B384BCF0--