On Nov 30, 2005, at 4:30 PM, Ruediger Pluem wrote:
I believe the clearer approach would be to fetch the connection
from the connection pool
each time and do not use this module config method any longer. This
would also resolve the
problem of Hans-Joerg which you fixed with your recent
Jim Jagielski [EMAIL PROTECTED] writes:
Can you try HEAD on httpd-trunk for a fix until something
more robust as far as the connections are implemented...
It gets the backend-connections right, but segfaults in the new code in
proxy_util.c.
I got the following out of a coredump:
dbx:
On Nov 29, 2005, at 4:55 PM, Ruediger Pluem wrote:
On 11/29/2005 04:12 PM, Jim Jagielski wrote:
Can you try HEAD on httpd-trunk for a fix until something
more robust as far as the connections are implemented...
Just for convenience:
http://svn.apache.org/viewcvs?rev=349723view=rev
Has
On 11/30/2005 08:38 PM, Jim Jagielski wrote:
On Nov 29, 2005, at 4:55 PM, Ruediger Pluem wrote:
[..cut..]
Has someone found out out why we close the connection if
r-proxyreq == PROXYREQ_PROXY || r-proxyreq == PROXYREQ_REVERSE?
I fear that this is something that has survived from 2.0.x.
Can you try HEAD on httpd-trunk for a fix until something
more robust as far as the connections are implemented...
On 11/29/2005 04:12 PM, Jim Jagielski wrote:
Can you try HEAD on httpd-trunk for a fix until something
more robust as far as the connections are implemented...
Just for convenience:
http://svn.apache.org/viewcvs?rev=349723view=rev
Has someone found out out why we close the connection if
It seems to me that is_address_reusable should be
assumed to be 0 if either
(r-proxyreq == PROXYREQ_PROXY || r-proxyreq == PROXYREQ_REVERSE)
As mentioned, we go ahead and force close the socket
anyway, the problem is that conn-hostname still
points to the wrong element. So:
if
On 11/23/2005 06:11 PM, Jim Jagielski wrote:
It seems to me that is_address_reusable should be
assumed to be 0 if either
(r-proxyreq == PROXYREQ_PROXY || r-proxyreq == PROXYREQ_REVERSE)
As mentioned, we go ahead and force close the socket
Does anybody remember why we close the
Ruediger Pluem wrote:
On 11/23/2005 06:11 PM, Jim Jagielski wrote:
It seems to me that is_address_reusable should be
assumed to be 0 if either
(r-proxyreq == PROXYREQ_PROXY || r-proxyreq == PROXYREQ_REVERSE)
As mentioned, we go ahead and force close the socket
Does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rüdiger, Jim,
I used the tarball from http://people.apache.org/~pquerna/dev/httpd-2.1.10/.
Ruediger Pluem [EMAIL PROTECTED] writes:
[...]
I think the real problem happens if you have requests to different backends
(webapp-cluster,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I briefly tried httpd-2.1.10 today and still see this.
(Same httpd.conf, only changed ServerRoot to
/usr/local/apache2-2.1.10/)
kind regards
Hansjörg
Hansjoerg Pehofer [EMAIL PROTECTED] writes:
Hi,
I experienced Apache-2.1.7 (/w WorkerMPM
Thanks for the report: You said that you tested against
2.1.10-HEAD right?
On Nov 21, 2005, at 10:25 AM, Hansjoerg Pehofer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I briefly tried httpd-2.1.10 today and still see this.
(Same httpd.conf, only changed ServerRoot to
On 11/21/2005 06:52 PM, Jim Jagielski wrote:
Thanks for the report: You said that you tested against
2.1.10-HEAD right?
On Nov 21, 2005, at 10:25 AM, Hansjoerg Pehofer wrote:
Hi,
I briefly tried httpd-2.1.10 today and still see this.
(Same httpd.conf, only changed ServerRoot to
Hi,
I experienced Apache-2.1.7 (/w WorkerMPM on Solaris 9) connecting to the
wrong backends when having configured more than one balancer cluster.
(see httpd.conf below)
ErrorLog shows some odd entries (marked in the example below) during
proxy_util.c's ap_proxy_determine_connection().
I could
14 matches
Mail list logo
