I have just found out that weighttp keep alive option was set but I didn't tell uwsgi to keep alive so it was closing the connections after request, thus making "error: read() failed: Connection reset by peer (104)" pop up and failing half of the requests
adding: uwsgi_response_add_header(wsgi_req, (char *)"Connection", 10, (char *)"HTTP/1.1", 8); makes the http plugin to can_keepalive, however weighttp expects a "keep-alive" string to mark succeed++, which is what servers send, anyway to change this? Thanks, 2014-07-17 17:43 GMT-03:00 Daniel Nicoletti <[email protected]>: > hi, > > I'm running weighttp to measure my app performance > and so far I get lots of: > error: read() failed: Connection reset by peer (104) > The application only writes a reply with > "hello world" > at first I thought it was some OS limit but the > same doesn't happen to nginx. > > Any tips on what could be happening? > > Thanks > > -- > Daniel Nicoletti > > KDE Developer - http://dantti.wordpress.com -- Daniel Nicoletti KDE Developer - http://dantti.wordpress.com _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
