Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
From: bugzilla@apache.org
To: dev@tomcat.apache.org
Subject: [Bug 53829] Timed out websocket hangs on send
Date: Wed, 05 Sep 2012 23:01:27 +0000
Message-ID: <bug-53829-78-li6XiA714O@https.issues.apache.org/bugzilla/>
In-Reply-To: <bug-53829-78@https.issues.apache.org/bugzilla/>
References: <bug-53829-78@https.issues.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated
MIME-Version: 1.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=53829

Mark Thomas <markt@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #2 from Mark Thomas <markt@apache.org> ---
Firefox doesn't close the connection, so since WebSocket uses an infinite
timeout by default, Tomcat just sits and waits for Firefox so send some data.
As soon as I close Firefox, the thread is released.

Possible work-arounds are:
- use a different browser (e.g. Chrome it didn't time out after a couple of
minutes in my simple test)
- specify a read timeout for the WebSocket app and then use ping/pongs to keep
the connection alive

You may also want to report a bug against Firefox since the onClose() event is
firing but the socket is remaining open.

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org