They are using different processes, doesn't that separate them?
On May 3, 12:00 am, Graham Dumpleton graham.dumple...@gmail.com
wrote:
If you are receiving requests for same application on both ports, then yes.
Graham
2009/5/2 Alex Robbins alexander.j.robb...@gmail.com:
Sorry
it to both?
Thanks,
Alex
On Apr 30, 1:47 am, Graham Dumpleton graham.dumple...@gmail.com
wrote:
2009/4/18 Alex Robbins alexander.j.robb...@gmail.com:
When you say 'Also, I get no errors if I remove the maximum-requests',
is that on all configurations?
Yes, that fixes it in all of the cases
When you say 'Also, I get no errors if I remove the maximum-requests',
is that on all configurations?
Yes, that fixes it in all of the cases.
When you run your tests, are requests always sequential? Ie., no
concurrent requests.
No, the url checker is threaded, it normally runs 10 concurrent
The urls that not working aren't using anything except the plain
django 1.0.2. (No GeoDjango). So it could be django. How would
increasing the max requests make it more thread-safe?
On Apr 15, 4:03 pm, Ariel Mauricio Nunez Gomez
ingenieroar...@gmail.com wrote:
Bah, I didn't realize it was an
I am seeing this same error. I tried a little bit of experimentation.
Does this give you any clues as to what might be happening?
I wrote a script that runs through the same list of urls (58) on my
site.
Every run produces different errors and different numbers of errors,
but some setups seem
Also, I get no errors if I remove the maximum-requests
On Apr 15, 3:45 pm, Alex Robbins alexander.j.robb...@gmail.com
wrote:
I am seeing this same error. I tried a little bit of experimentation.
Does this give you any clues as to what might be happening?
I wrote a script that runs through
