[web2py] Re: Rocket with urllib2 behavior [BUG?]

2011-02-06 Thread Timbo
If you've only got one thread running, then yes, this will deadlock on any threaded server. Rocket was certainly not made to not allow lookups back to itself. Where are you putting this code? If by assigning to response are you masking web2py's response object? I... 1) downloaded a fresh copy

[web2py] Re: Rocket with urllib2 behavior [BUG?]

2011-02-06 Thread Timbo
I had one more thought, does '/server/default/index' point to this code? If this is the case, then you have an infinite loop that consumes all available threads and deadlocks. Again, this is not a rocket-specific behavior. On Feb 6, 10:08 am, Timbo tfarr...@owassobible.org wrote: If you've

[web2py] Re: Rocket with urllib2 behavior [BUG?]

2011-02-06 Thread Massimo Di Pierro
wait... def index(): import urllib2 url = 'http://127.0.0.1:8000/welcome/default/index' resp = urllib2.urlopen(url).read() return resp + blah This creates an infinite loops that spans more and more threads. I assumed from the original post, the urllopen code was outside a

[web2py] Re: Rocket with urllib2 behavior [BUG?]

2011-02-06 Thread Timbo
It only creates infinite loops if it's in the welcome application...which it isn't (as I specified in step 2). In either case, we still need more information. On Feb 6, 12:04 pm, Massimo Di Pierro massimo.dipie...@gmail.com wrote: wait... def index():     import urllib2     url =

[web2py] Re: Rocket with urllib2 behavior [BUG?]

2011-02-06 Thread vihang
As Tim rightly put it, the issue was only when called from the same controller. The chances of that happening are very bleak and in our case a mere coincidence. Nevertheless we wanted it cleared just to understand the server better. We have remodeled our code.