Re: websockets holding on to threads.

2013-04-09 Thread Mark Thomas
On 08/04/2013 15:32, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chuck, On 4/8/13 8:30 AM, Caldarale, Charles R wrote: From: Anton Piatek1 [mailto:anton.pia...@uk.ibm.com] Subject: Re: websockets holding on to threads. My thinking about it being a bug is that

Re: websockets holding on to threads.

2013-04-08 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chuck, On 4/8/13 8:30 AM, Caldarale, Charles R wrote: >> From: Anton Piatek1 [mailto:anton.pia...@uk.ibm.com] Subject: Re: >> websockets holding on to threads. > >> My thinking about it being a bug is that to support N clien

RE: websockets holding on to threads.

2013-04-08 Thread Anton Piatek1
"Caldarale, Charles R" wrote on 08/04/2013 13:30:00: > From: "Caldarale, Charles R" > > From: Anton Piatek1 [mailto:anton.pia...@uk.ibm.com] > > My thinking about it being a bug is that to support N clients with > > websockets, you need N threads available on tomcat, even though they are >

Re: websockets holding on to threads.

2013-04-08 Thread Howard W. Smith, Jr.
On Mon, Apr 8, 2013 at 8:30 AM, Caldarale, Charles R < chuck.caldar...@unisys.com> wrote: > > From: Anton Piatek1 [mailto:anton.pia...@uk.ibm.com] > > Subject: Re: websockets holding on to threads. > > > My thinking about it being a bug is that to support N clients with

Re: websockets holding on to threads.

2013-04-08 Thread Howard W. Smith, Jr.
On Mon, Apr 8, 2013 at 4:05 AM, Anton Piatek1 wrote: > > > Multiple tabs/windows is one thing, but multiple clients are just as big a > problem. > Not a problem or a concern in my web app. Endusers are trained to use the web app in 'one' browser tab/window 'per device'; every now and then, I can

RE: websockets holding on to threads.

2013-04-08 Thread Caldarale, Charles R
> From: Anton Piatek1 [mailto:anton.pia...@uk.ibm.com] > Subject: Re: websockets holding on to threads. > My thinking about it being a bug is that to support N clients with > websockets, you need N threads available on tomcat, even though they are > only getting updates every

Re: websockets holding on to threads.

2013-04-08 Thread Anton Piatek1
"Howard W. Smith, Jr." wrote on 05/04/2013 21:22:33: > On Fri, Apr 5, 2013 at 9:07 AM, Anton Piatek1 wrote: > > > I am seeing what at first appears to be a bug, but given the lack of other > > reports I can't believe I am the only person seeing this, so maybe it is > > user-error. > > > > I h

Re: websockets holding on to threads.

2013-04-05 Thread Howard W. Smith, Jr.
On Fri, Apr 5, 2013 at 9:07 AM, Anton Piatek1 wrote: > I am seeing what at first appears to be a bug, but given the lack of other > reports I can't believe I am the only person seeing this, so maybe it is > user-error. > > I have tomcat (was 7.0.30, but I just tried with 7.0.39) running a website

websockets holding on to threads.

2013-04-05 Thread Anton Piatek1
I am seeing what at first appears to be a bug, but given the lack of other reports I can't believe I am the only person seeing this, so maybe it is user-error. I have tomcat (was 7.0.30, but I just tried with 7.0.39) running a website which uses websockets. The websockets code in tomcat isn't t