Are you deploying with egg:gearbox#wsgiref as your server? Keep in mind that wsgiref is only mean for development and accepts a single request at time. On production environments you want at least to deploy on a multithreaded server like egg:waitress#main
On Wed, Feb 5, 2014 at 3:17 PM, pkraus <[email protected]> wrote: > Let me start by stating the following problem does not happen on any of > the prior versions of TG. > > We have a local proxy that half are users use for monitoring purposes. > > These users have no problems accessing any of the development servers when > running gearbox serve. > > Non proxy (WINDOWS ONLY) clients when they connect they lockup the server > causing causing timeouts and stop anyone else from accessing it. Again > these are the guys NOT on the proxy using any browser ie,chrome,and firefox. > > It's driving me nuts and i can't make an sense of it. other versions of TG > no issues. > > Thoughts? Suggestions? > > right now i just force my testers to put themselves on the proxy but its > still a pain in the butt. > > TIA > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/turbogears. > For more options, visit https://groups.google.com/groups/opt_out. > -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/turbogears. For more options, visit https://groups.google.com/groups/opt_out.
