already responded

[Brad Fitzpatrick]

When you say "the problem goes away", do you see a real problem, or just
the error messages?

I honestly hardly run at debug level >= 3, so it's possible the warning
messages are bogus, or a legacy of times before persistent connections.

Before I look into this more, I'm curious if things actually work for you,
despite the warnings.  If not, then I'm curious what your traffic looks
like, and the rest of your config.

- Brad


On Fri, 11 May 2007, Justin Huff wrote:

> While testing perlbal we ran into these messages:
> 	already responded.
> 	already responded [2].
> They start immediately after perlbal has parsed the headers -- before a
> backend connection is created.
>
> They seem to happen occasionally on a POST that's preceded by a GET.
> If I get persist_client to off, the problem goes away.
>
> Any ideas?
>
> Thanks!
> --Justin
>
>