[noPoll] Websocket diconnect issues -- stress test

[Kale, Rahul]

Hello,

Since we have a critical dependency on noPoll library, I embarked
on creating a simple client/server test program using just the noPoll library
in isolation to be able to run stress tests against it.

I have uploaded the test code in GitHub at:

https://github.com/rpkale/test-nopoll

The README file explains the test case and usage of the binary.

First the good news:

The abrupt disconnect issue I had reported earlier (which you fixed in the
latest version) can be reproduced in minutes instead of hours/days in our
production code base. This is the issue regarding occasional split headers
arriving at the client.
If you run one nopoll_test client instance against a nopoll_test server
instance on a different host, you will see that it disconnects within a
minute or two with the earlier version of the library. Compiling against your
latest version of noPoll, it always survives. If you enable nopoll internal
logs, you can see that the recovery condition is hit quite often. Since now only
noPoll library implementation is in the picture, this validates that the
split headers are indeed in the TCP layer and a not a server implementation
artifact.

Once again thanks for taking the effort in fixing this issue since it would
have affected all users of the library.

One side note: the internal log messages for this condition is a little
misleading. It currently says 'disconnecting' and them recovers instead.
You may want to clean it up at some point.

I have a couple of other unrelated issues that this test case brings out.
I will post separate emails for them.

Regards,

Rahul

Rahul Kale

IP Video Systems
Barco, Inc
1287 Anvilwood Ave
Sunnyvale, CA  94089

Tel  +1 408 400 4238

This message is subject to the following terms and conditions: MAIL DISCLAIMER<http://www.barco.com/en/maildisclaimer>
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <http://lists.aspl.es/pipermail/nopoll/attachments/20160602/69ab86f4/attachment.html>