On 03/11/2013 02:29, Bob DeRemer wrote:
BACKGROUND: We've created a test client that spins up multiple
websocket clients - each in their own thread. While using their own
thread isn't very resource efficient, that's ok. We want each
client's send/receive to be isolated from each other. Our
-Original Message-
From: Mark Thomas [mailto:ma...@apache.org]
Sent: Sunday, November 03, 2013 11:24 AM
To: Tomcat Users List
Subject: Re: weird behavior using Tomcat 7 JSR-356 client implementation in
standalone multi-threaded test client
On 03/11/2013 02:29, Bob DeRemer wrote:
During our testing of large scale websocket connections going through Amazon
ELB, we've found that ELB will timeout idle TCP connections after 60 seconds.
Our testing scenarios is one where we want to ramp up 10(s) of 1000s of
websocket connections - then, after they are all connected, start
-Original Message-
From: Bob DeRemer [mailto:bob.dere...@thingworx.com]
Sent: Sunday, November 03, 2013 8:31 PM
To: Tomcat Users List
Subject: Can Tomcat 7 jsr-356 plumbing be configured to automatically send
websocket ping/pong on a specified interval?
During our testing of
On Mon, Nov 4, 2013 at 5:52 AM, Bob DeRemer bob.dere...@thingworx.comwrote:
-Original Message-
From: Bob DeRemer [mailto:bob.dere...@thingworx.com]
Sent: Sunday, November 03, 2013 8:31 PM
To: Tomcat Users List
Subject: Can Tomcat 7 jsr-356 plumbing be configured to
