On 12/17/2008 12:38 AM, Jess Holle wrote: > The errno assignments you added did the trick. > > Unfortunately, I'm still missing the overall goal. I have many proxy > balance members like: > > BalancerMember ajp://localhost:8010 route=tomcat1 min=16 max=80 > smax=40 ttl=900 keepalive=Off timeout=90000 retry=30 > connectiontimeout=160ms flushpackets=on > > BalancerMember ajp://localhost:8011 route=tomcat2 min=16 max=80 > smax=40 ttl=900 keepalive=Off timeout=90000 retry=30 > connectiontimeout=160ms flushpackets=on > > ... > > However, the error log says: > > [Tue Dec 16 17:32:*25* 2008] [error] (OS 10061)No connection could be > made because the target machine actively refused it. : proxy: AJP: > attempt to connect to 127.0.0.1:8011 (localhost) failed > [Tue Dec 16 17:32:25 2008] [error] ap_proxy_connect_backend disabling > worker for (localhost) > [Tue Dec 16 17:32:25 2008] [error] proxy: AJP: failed to make > connection to backend: localhost > > [Tue Dec 16 17:32:*26* 2008] [error] (OS 10061)No connection could be > made because the target machine actively refused it. : proxy: AJP: > attempt to connect to 127.0.0.1:8012 (localhost) failed > [Tue Dec 16 17:32:26 2008] [error] ap_proxy_connect_backend disabling > worker for (localhost) > [Tue Dec 16 17:32:26 2008] [error] proxy: AJP: failed to make > connection to backend: localhost > ... > > Each port (on Windows) still consistently takes right around 1 full > second to reject. despite having set connectiontimeout to be 160ms. > > Something seems to still be awry here as 160ms is significantly less > than 1000ms...
I guess you should move this over to d...@apr as this is likely a problem with the windows specific connect call not returning immediately. Regards Rüdiger
