On Oct 31, 3:56 am, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> On 30-Oct-07, at 10:55 PM, webjunkie wrote:
>
> >> Err, what was the old version, and what's the new version?
>
> >> "Upgrade" is kind of vague. :-/
>
> > Upgraded from 3.2.10 to 3.3.1 ;)
>
> which is 8 months old ;-)
and still n
On 30-Oct-07, at 10:55 PM, webjunkie wrote:
>> Err, what was the old version, and what's the new version?
>>
>> "Upgrade" is kind of vague. :-/
>
> Upgraded from 3.2.10 to 3.3.1 ;)
which is 8 months old ;-)
--
regards
kg
http://lawgon.livejournal.com
http://nrcfosshelpline.in/web/
--~--~
On Oct 31, 4:25 am, webjunkie <[EMAIL PROTECTED]> wrote:
> On Oct 30, 4:53 pm, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
>
>
>
> > Err, what was the old version, and what's the new version?
>
> > "Upgrade" is kind of vague. :-/
>
> Upgraded from 3.2.10 to 3.3.1 ;)
Except that I still can't see
On Oct 30, 4:53 pm, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote:
>
> Err, what was the old version, and what's the new version?
>
> "Upgrade" is kind of vague. :-/
Upgraded from 3.2.10 to 3.3.1 ;)
--~--~-~--~~~---~--~~
You received this message because you are subs
On 10/30/07, webjunkie <[EMAIL PROTECTED]> wrote:
>
> I had the same problem today. I can confirm that it's fixed with a
> newer mod_python.
> http://groups.google.com/group/django-users/browse_frm/thread/5718bb2a94ebec2
>
Err, what was the old version, and what's the new version?
"Upgrade" is k
I had the same problem today. I can confirm that it's fixed with a
newer mod_python.
http://groups.google.com/group/django-users/browse_frm/thread/5718bb2a94ebec2
On Oct 26, 6:59 am, Chris Henderson wrote:
> I ran into this when I was running benchmarks with ab2 on an Ubuntu
> Dapper box. I en
On Oct 26, 3:59 pm, Chris Henderson wrote:
> I ran into this when I was running benchmarks with ab2 on an Ubuntu
> Dapper box. I ended up just using the patch that you provided to fix
> the problem, but after I installed gutsy recently, I noticed that the
> problem was no longer occurring on a
I ran into this when I was running benchmarks with ab2 on an Ubuntu
Dapper box. I ended up just using the patch that you provided to fix
the problem, but after I installed gutsy recently, I noticed that the
problem was no longer occurring on a straight svn Django checkout
(without the fix). It
Don't see no harm in adding the close() hook, but as mr. Batchelder
said, I'd say it's the wrong thing to do.
If the connections really are dangling, I'd say there's a much larger
issue to deal with.
Sincerely,
Ludvig Ericson
On Aug 11, 1:57 am, Ned Batchelder <[EMAIL PROTECTED]> wrote:
> This
This rang some bells about a problem we'd had with memcached, so I asked
Dave St. Germain (our goto guy for issues like this). Here's what he
had to say:
I think this is the wrong fix for the problem. memcached
connections are supposed to be persistent, not torn down after every
re
Hi all --
We've noticed that in a few cases Django under mod_python can leave
dangling connections to memcached open. We've had trouble tracking
down the circumstances under which this happens, but when it does it
can lead to memcached servers hitting their connection limits, which
means caching
11 matches
Mail list logo