This happens when i have one connection to the tomcat jboss server.

Regards

Ben Cuthbert
Deutsche Bank AG
Corporate & Investment Bank
GTO : TISO / Arch Global Finance / Prime Services
PGP: http://pgp.mit.edu
+44 (0) 20 754 76389 (Tel)
+44 (0) 20 754 74996 (Fax)



Rainer Jung <[EMAIL PROTECTED]>

11/07/2006 09:51 PM

Please respond to
dev@httpd.apache.org

To
dev@httpd.apache.org
cc
Subject
Re: Apache BUG: 36495  : ajp_proxy_connect_backend failure





Hi,

adding to Mladens advice: is it possible, that you are trying to produce
more connections, than configured worker threads on your tomcat connector?

Does the error only show up under high load?
How many connections to 1.1.1.2:8009 in which state do you have, when
the error appears?

netstat -an | fgrep '1.1.1.2.8009' | \
awk '{print $NF}' | sort | uniq -c

How do these numbers relate to the number of threads configured in the
connector elements of your tomcats server.xml?

Regards,

Rainer

Benjamin Cuthbert schrieb:
>
> All
>
> I have apache 2.2.0 setup on Solaris and i am running into the same
> issues as the bug here, any had any updates on this.
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=36495
>
>
> Error i get is:
>
> [Mon Nov 06 16:35:35 2006] [error] proxy: AJP: failed to make connection
> to backend: 1.1.1.2
> [Mon Nov 06 16:36:35 2006] [error] (146)Connection refused: proxy: AJP:
> attempt to connect to 1.1.1.2:8009 (1.1.1.2) failed
> [Mon Nov 06 16:36:35 2006] [error] ap_proxy_connect_backend disabling
> worker for (1.1.1.2)
> [Mon Nov 06 16:36:35 2006] [error] proxy: AJP: failed to make connection
> to backend: 1.1.1.2
>
> Does anyone know if this bug was fixed ?
>
>
> ---
>
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.



---

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.

Reply via email to