Adrian Holovaty wrote: > On 11/7/06, Jakub Labath <[EMAIL PROTECTED]> wrote: > > If you take a look at the attached log you will see the same child > > process having the same request._req object for two different IP > > addresses. Now this should not normally happen should it. The memory > > address of response object also matches. It also matches the time when > > the users noticed it. > > > > I'll be upgrading both apache2 and mod python soon to their latest > > versions, we'll see if this happens again. > > Hi Jakub, > > Do you have any updates on this problem? Was it a mod_python bug?
FWIW, on the mod_python list when he brought this to us we couldn't see anything that would suggest specifically that it would be a mod_python problem and also questioned whether there were intermediate caches involved. In respect of the request object being the same address as he illustrated, there is no reason why this could not happen purely through memory reuse. That there can be multiple Apache child processes involved can also make it more confusing. Suggestions given were to output the mod_python req.connection.id and req.connection.remote_ip members and see if they change between requests to confirm they are unique requests. Also putting out the process ID of the Apache child process handling the request would probably be a good idea as well. Anyway, they said they would go off and try some other things, but I don't recollect them ever coming back to the mod_python list and saying they resolved it. All up though, we believe it highly unlikely that it is a problem with mod_python. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
