ajp and mod_proxy_balancer are rapidly improving,
> seriously try the latest (2.2.11).
>
> Regards,
>
> Rainer
>
> On 06.05.2009 14:41, Arne Riecken wrote:
> > I need to either close the ajp connections or send keepalive messages
> > because there is a firewall with
I need to either close the ajp connections or send keepalive messages
because there is a firewall with a timeout of 1h between the mod_proxy_ajp
(Apache 2.2.9) and the JBoss Server with ajp connector and
in server.xml.
Setting
BalancerMember ajp://hostname status=-H ping=3 smax=0 ttl=600
did
Hello,
question about keepalive for mod_proxy (via ProxyPass directive) AJP
connections:
"This flag will tell the Operating System to send KEEP_ALIVE messages on
inactive connections (interval depends on global OS settings, generally
120ms)"
(http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#pr
Thanks, I did that bevore posting but did not understand id clearly. There
is written:
"Any connections above smax are subject to a time to live or ttl. Apache
will never create more than the Hard Maximum or max connections to the
backend server."
"smax [...] Upto the Soft Maximum number of conne
Hello,
in the past I used mod_jk with workers with connection_pool_timeout=600 and
tomcat ajp connector with corresponding connectionTimeout=60 as
recommended.
Now I additionally want to use mod_proxy_ajp with apache 2.2.9. Where in
apache httpd do I honour the tomcat connectionTimeout=60
If I understood right, Apache httpd 1.3 is not multi threaded but can
consist of multiple processes. And one Apache process has a connection pool
size of 1 that should not be changed. So is there a kind of pool of
1-connection-pools ? Is it right that it does not make sense then for mod_jk
to have
Thanks for Your answer.
There are at least two (watchdog) ajp requests through the web server to the
workers every minute, and as i wrote, the ajp connection_pool_timeout ist
600, connectionTimeout in Tomcats server.xml is accordingly 60. So I
cannot image how the web server can be more idle t
Hi,
please have a look at the mod_jk.log. Can anyone say if these info-entrys
are normal or if the system is unhealthy? Or might the network be bad? These
entrys come at least two times per hour.
Thanks.
mod_jk 1.2.23
Apache 1.3.34
Tomcat 5.5.20
socket_keepalive=False
connect_timeout=3
prep
