From users-return-243046-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org Tue Aug 6 12:21:25 2013 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 E4A82FFA5 for ; Tue, 6 Aug 2013 12:21:25 +0000 (UTC) Received: (qmail 49388 invoked by uid 500); 6 Aug 2013 12:21:22 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 49170 invoked by uid 500); 6 Aug 2013 12:21:22 -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 49155 invoked by uid 99); 6 Aug 2013 12:21:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Aug 2013 12:21:21 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bob.deremer@thingworx.com designates 207.46.163.205 as permitted sender) Received: from [207.46.163.205] (HELO na01-bl2-obe.outbound.protection.outlook.com) (207.46.163.205) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Aug 2013 12:21:12 +0000 Received: from BLUPR06MB193.namprd06.prod.outlook.com (10.242.191.143) by BLUPR06MB196.namprd06.prod.outlook.com (10.242.191.151) with Microsoft SMTP Server (TLS) id 15.0.731.12; Tue, 6 Aug 2013 12:20:25 +0000 Received: from BLUPR06MB193.namprd06.prod.outlook.com ([169.254.13.15]) by BLUPR06MB193.namprd06.prod.outlook.com ([169.254.13.15]) with mapi id 15.00.0731.000; Tue, 6 Aug 2013 12:20:24 +0000 From: Bob DeRemer To: Tomcat Users List Subject: RE: any known problems using Tomcat 7.0.42 apr/native (windows) with websockets? Thread-Topic: any known problems using Tomcat 7.0.42 apr/native (windows) with websockets? Thread-Index: Ac6SDmn5qh/O+heCR9+M5ZHl18XMqQAa/4aAAAkJNZA= Date: Tue, 6 Aug 2013 12:20:24 +0000 Message-ID: References: <73c06e964fa7482883cc8a666fee0552@BLUPR06MB193.namprd06.prod.outlook.com> <5200AC17.1010501@apache.org> In-Reply-To: <5200AC17.1010501@apache.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [98.237.127.73] x-forefront-prvs: 0930AAFAD9 x-forefront-antispam-report: SFV:NSPM;SFS:(5423002)(252514010)(24454002)(479174003)(377454003)(199002)(13464003)(189002)(51704005)(74706001)(33646001)(83322001)(19580405001)(19580395003)(76576001)(74316001)(63696002)(76796001)(74662001)(49866001)(76786001)(31966008)(79102001)(81542001)(81342001)(80022001)(77096001)(53806001)(74366001)(56816003)(16406001)(77982001)(59766001)(47446002)(74502001)(47976001)(74876001)(50986001)(54356001)(80976001)(46102001)(4396001)(47736001)(69226001)(56776001)(66066001)(76482001)(54316002)(83072001)(51856001)(65816001)(24736002);DIR:OUT;SFP:;SCL:1;SRVR:BLUPR06MB196;H:BLUPR06MB193.namprd06.prod.outlook.com;CLIP:98.237.127.73;RD:InfoNoRecords;A:1;MX:1;LANG:en; Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: thingworx.com X-Virus-Checked: Checked by ClamAV on apache.org > -----Original Message----- > From: Mark Thomas [mailto:markt@apache.org] > Sent: Tuesday, August 06, 2013 3:56 AM > To: Tomcat Users List > Subject: Re: any known problems using Tomcat 7.0.42 apr/native (windows) > with websockets? >=20 > On 06/08/2013 03:45, Bob DeRemer wrote: > > QUESTION > > > > Is anyone aware of any problems using the apr/native connector + > > websockets in Tomcat 7.0.42? >=20 > I'm not aware of any reports. >=20 > > BACKGROUND > > > > We are trying to see how many concurrent websocket connections Tomcat > > will handle running on Windows Server. We wrote a multi-threaded java > > console app that spins up a thread-per simulated websocket client. In > > each thread, we are using a separate Ning websocket client. > > Unfortunately, we can't connect more than a few connections before we > > start getting websocket errors. >=20 > What sort of errors? I believe the connection was being closed unexpectedly >=20 > > If we change the connector to use NIO, the sporadic connection errors > > seem to go away, but then we find that after about 200 connections, > > the communication seems to hang. This happens if all connections are > > made from a single test client instance or spread across multiple > > client instances. >=20 > That suggests at least some issue with APR/native and WebSocket. >=20 > > We're trying to determine where the problem lies and if it's in our > > use of Ning in a multi-threaded client app, Tomcat connector > > configuration, use of Tomcat websockets on Windows or something else. >=20 > The focus in Tomcat 7 is going to move to the JSR356 implementation prett= y > soon. I'd suggest looking at that rather than putting effort into Tomcat = 7's > current implementation. Are there any examples for what must be written server-side? Also, is there a version of Tomcat (7 or 8) that has this functionality ava= ilable to test against? >=20 > > If anyone has any suggestions, I would greatly appreciate it. If you > > need additional information, please don't hesitate to ask. >=20 > I'll look into adding a concurrent client test to the Tomcat unit tests. >=20 > Mark >=20 Bob >=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