Roberto, There is no problem with this, i created a test with twitterapi and everythin worked fine. I think the problem is my database connection on the other end.
Thanks Regards Alan On Mon, Nov 8, 2010 at 6:48 PM, Alan Castro <[email protected]> wrote: > This only happens in multiprocessing mode and I have the same code in > production running without multiprocessor. > > One more thing to be added to the discussion is that I make 4 asynchronous > ajax calls to the webserver. And in production (without multiprocessor) I > always have +-300ms response times. > > This problem happens everytime I use this configuration with > httplib.HTTPConnection. > > I'll create a dummy application here to verify this > > > On Mon, Nov 8, 2010 at 6:01 PM, Roberto De Ioris <[email protected]> wrote: > >> >> > I have this: >> > >> > SIGPIPE: writing to a closed pipe/socket/fd (probably the client >> > disconnected) on request /artist/show/12553 !!! >> > write(): Broken pipe [pyutils.c line 101] >> > >> >> >> This is very strange, it could be that the timeout of your webserver is >> too low, but why it appears only in multiprocessing mode ? >> >> It makes no sense for me. >> >> The error is 100% reproducible ? >> >> The only thing that can lead to this kind of problems in pylons is having >> debug enabled, but a big warning during startup should get your attention. >> >> >> http://wiki.pylonshq.com/display/pylonscookbook/Production+deployment+using+mod_python >> >> >> -- >> Roberto De Ioris >> http://unbit.it >> _______________________________________________ >> uWSGI mailing list >> [email protected] >> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >> > >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
