Hi Prashant,
On Tue, Jun 17, 2014 at 2:40 PM, Prashant Deva
wrote:
> ok running on tomcat 8.0.8 with spring 4.0.5 and reactor 1.1.2, my log
> within minutes gets filled with these exceptions.
>
> Seems like it could be a tomcat issue after all:
>
This error could be also read as: the client (th
ok running on tomcat 8.0.8 with spring 4.0.5 and reactor 1.1.2, my log
within minutes gets filled with these exceptions.
Seems like it could be a tomcat issue after all:
11:35:37,922 ERROR http-nio-80-exec-37
handler.LoggingWebSocketHandlerDecorator:61 - Transport error for SockJS
session id=hv4nc
just noticed this, you tried running on tomcat 8, while we are running
7.0.53...
Prashant
On Mon, Jun 16, 2014 at 1:36 PM, Prashant Deva
wrote:
> our production instance (which we are running into issues with) has about
> 2500 concurrent users.
>
> Prashant
>
>
> On Mon, Jun 16, 2014 at 1:26 P
our production instance (which we are running into issues with) has about
2500 concurrent users.
Prashant
On Mon, Jun 16, 2014 at 1:26 PM, Rossen Stoyanchev <
rstoyanc...@gopivotal.com> wrote:
> On Mon, Jun 16, 2014 at 4:04 PM, Prashant Deva
> wrote:
>
> > Rossen,
> > Did you use an external
On Mon, Jun 16, 2014 at 4:04 PM, Prashant Deva
wrote:
> Rossen,
> Did you use an external queue?
Yes I did have the sample configured to use RabbitMQ for broadcasting
messages. That's running as a separate process though so it shouldn't
change the output of "lsof".
How many clients were conne
Rossen,
Did you use an external queue? How many clients were connected at the same
time?
Prashant
On Mon, Jun 16, 2014 at 12:02 PM, Rossen Stoyanchev <
rstoyanc...@gopivotal.com> wrote:
> I gave this a quick try with the spring-websocket-portfolio sample [1] with
> Tomcat 8. The output of the
I gave this a quick try with the spring-websocket-portfolio sample [1] with
Tomcat 8. The output of the lsof command is just over 200 initially and
then goes up a little but not much (about 10).
>From the client-side I configured the SockJS client to use the WebSocket
transport (i.e. using Tomcat'
hmm, we are just using spring websockets to send messages. In fact there is
only two 'topics' in total, so there isnt much the application is doing
quite frankly.
do you think this is a spring issue?
Prashant
On Mon, Jun 16, 2014 at 10:10 AM, David kerber wrote:
> On 6/16/2014 12:57 PM, Prasha
On 6/16/2014 12:57 PM, Prashant Deva wrote:
I am using Tomcat 7.0.53 with Spring 4 websockets (spring's SockJS support).
I notice that tomcat opens thousands of files.
Correction: your application opens thousands of files, or leaves them
open when it should have closed them.
Just running
I am using Tomcat 7.0.53 with Spring 4 websockets (spring's SockJS support).
I notice that tomcat opens thousands of files.
Just running for a few hours I noticed, it opened 16,552 files:
root@dripcast:~# lsof -p 22691 | wc -l
16552
Our logs are full of this exception thrown tons of times every s
10 matches
Mail list logo
