On Wed, Mar 2, 2011 at 8:54 AM, Roberto De Ioris <[email protected]> wrote:
> This should be fixed now
hm, no, but I'm not able to track down the culprit
I think it's related with this :
env1 = {}
env1['TEST'] = '\x00aaa'*10000
uwsgi.erlang_send_message(uwsgi_erlang, qs["process"][0], tuple(env1.items()) )
for j in uwsgi.erlang_recv_message(uwsgi_erlang):
yield str(j) + '\n'
uwsgi.erlang_close(uwsgi_erlang)
return
I have 18 bytes (expected ~ 40000)
[pid: 9725|app: 0|req: 1/1] 192.168.2.27 () {30 vars in 496 bytes}
[Wed Mar 2 10:32:39 2011] GET
/erlang?sname=uwsgierlang@johnII&process=echoer => generated 18 bytes
in 4 msecs (HTTP/1.1 200) 1 headers in 45 bytes (1 switches on core 0)
and a timeout
2011/03/02 10:33:39 [error] 6516#0: *195 upstream timed out (110:
Connection timed out) while reading upstream, client: 192.168.2.27,
server: localhost, request: "GET
/erlang?sname=uwsgierlang@johnII&process=echoer HTTP/1.1", upstream:
"uwsgi://127.0.0.1:38079", host: "192.168.2.27:38077"
--
luigi
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
