https://issues.apache.org/bugzilla/show_bug.cgi?id=47549
--- Comment #2 from [email protected] 2009-08-03 14:05:14 PST --- We had the following config: <Proxy balancer://sp_cluster> BalancerMember http://t1:48080 route=sp_server1 timeout=120 BalancerMember http://t2:48080 route=sp_server2 timeout=120 ProxySet stickysession=JSESSIONID </Proxy> But we got: Syntax error on line 12 of /home/webapp/apache/conf/vh.spportal.sp_cluster.conf: BalancerMember Connectiontimeout has wrong format The configuration is not proper, so the server spportal_server cannot start! We found that the bug somewhere here: if (ap_timeout_parameter_parse(val, &timeout, "s") != APR_SUCCESS) return "Connectiontimeout has wrong format"; But it is very complicated.. But from another forum a similar problem with release 2.2.11: Site index · List index Message view « Date » · « Thread » Top « Date » · « Thread » >From "Ian Lea" <[email protected]> Subject [us...@httpd] 2.2.11: BalancerMember Ping/Pong timeout has wrong format Date Wed, 31 Dec 2008 12:20:01 GMT Hi On apache 2.2.10 a config file with these lines <Proxy balancer://xxx> BalancerMember ajp://localhost:17100 route=yyy ping=10 </Proxy> works fine, but on 2.2.11 it fails to parse, showing error Syntax error on line 73 of /opt/apache-2.2.11/conf/test.conf: BalancerMember Ping/Pong timeout has wrong format I see that the changes file includes mod_proxy: Add the possibility to set the worker parameters connectiontimeout and ping in milliseconds. [Ruediger Pluem] If I've followed the code path correctly (far from certain), server/util.c says that the following units are understood * ms : milliseconds * s : seconds * mi[n] : minutes * h : hours but adding any of those makes no difference - they all still fail with the parse error. Any suggestions? Ian. [email protected] And also refer to this: https://issues.apache.org/bugzilla/show_bug.cgi?id=46500 -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
