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 (nike.apache.org: domain of bob.deremer@thingworx.com
 designates 207.46.163.210 as permitted sender)
From: Bob DeRemer <bob.deremer@thingworx.com>
To: Tomcat Users List <users@tomcat.apache.org>
Subject: RE: Is the current Tomcat 7 servlet websocket implementation being
 deprecated?
Thread-Topic: Is the current Tomcat 7 servlet websocket implementation being
 deprecated?
Thread-Index: Ac6SRrKFlSBxkGx5TuWKxoMHtF0/nQANCDWAAAkhGGA=
Date: Tue, 6 Aug 2013 12:22:21 +0000
Message-ID: 
 <3fdc730623904be4a1dc7842534e3fb6@BLUPR06MB193.namprd06.prod.outlook.com>
References: 
 <2acf9b8a99ab446898682e4ae3613675@BLUPR06MB193.namprd06.prod.outlook.com>
 <5200ACCB.1090607@apache.org>
In-Reply-To: <5200ACCB.1090607@apache.org>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


> -----Original Message-----
> From: Mark Thomas [mailto:markt@apache.org]
> Sent: Tuesday, August 06, 2013 3:59 AM
> To: Tomcat Users List
> Subject: Re: Is the current Tomcat 7 servlet websocket implementation bei=
ng
> deprecated?
>=20
> 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.
>=20
> No known issues or limitations but the JSR-356 will be ported to 7.0.x an=
d the
> current WebSocket implementation deprecated shortly (hopefully in the nex=
t
> few weeks).
>=20
> > 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=3D50000 and maxThreads=3D1000, so 200 concurrent
> > connections shouldn't be a problem.
>=20
> 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.
>=20
> > 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?
>=20
> I don't have any references for that but will be adding something to the =
unit
> tests.
>=20
> Mark
>=20

Thanks for the information.  If you have an reference examples for server-s=
ide code based on JSR356, as well as a drop of Tomcat that supports it, tha=
t would be a good place to start.

>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org


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