Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7D732F75C for ; Tue, 6 Aug 2013 07:59:15 +0000 (UTC) Received: (qmail 19439 invoked by uid 500); 6 Aug 2013 07:59:12 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 19353 invoked by uid 500); 6 Aug 2013 07:59:11 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 19343 invoked by uid 99); 6 Aug 2013 07:59:11 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Aug 2013 07:59:11 +0000 Received: from localhost (HELO s2laptop.home) (127.0.0.1) (smtp-auth username markt, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Aug 2013 07:59:10 +0000 Message-ID: <5200ACCB.1090607@apache.org> Date: Tue, 06 Aug 2013 09:59:07 +0200 From: Mark Thomas User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Is the current Tomcat 7 servlet websocket implementation being deprecated? References: <2acf9b8a99ab446898682e4ae3613675@BLUPR06MB193.namprd06.prod.outlook.com> In-Reply-To: <2acf9b8a99ab446898682e4ae3613675@BLUPR06MB193.namprd06.prod.outlook.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit On 06/08/2013 03:54, Bob DeRemer wrote: > I�ve seen some mention on the user and dev mailing lists that the > current servlet-based websocket implementation will be deprecated due to > the implementation of the JSR-356. We are currently implementing a > Tomcat 7-based websocket server implementation that we hoped could scale > up to at least 50K concurrent connections [or more], but are concerned > if there are any known issues and/or limitations with the websocket > implementation in Tomcat 7. No known issues or limitations but the JSR-356 will be ported to 7.0.x and the current WebSocket implementation deprecated shortly (hopefully in the next few weeks). > We are currently trying to test how high Tomcat 7 will scale with > regards to the maximum number of concurrent websocket connections, but > have already hit some problems with only 200+ concurrent connections. > Perhaps it�s our multi-threaded client, or Tomcat configuration � not > sure at this point. We have the Tomcat Connector configured with > maxConnections=50000 and maxThreads=1000, so 200 concurrent connections > shouldn't be a problem. It should scale but won't scale as well as the JSR-356 implementation is the current Tomcat 7 implementation is blocking within a frame. > If anyone could elaborate on the Tomcat 7 servlet websocket > implementation stability from a highly concurrent aspect that would be > great. Additionally, if anyone has achieved 10(s) of 1000(s) of > concurrent websocket connections with Tomcat 7, can you share how Tomcat > was configured, what OS it was running on, and what client library you > used in testing this? I don't have any references for that but will be adding something to the unit tests. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org