On 4/6/2012 5:52 PM, Pratapani wrote:
> Thanks for the replies.
> We are going to use "F5" for load balancing the Tomcat instances. As
> mentioned all the machines will share the same VIP.
> No Apache HTTP server for now !!
>
> I was able to use the session replication ( PersistenceManager) on tomc
Hi,
try to use envvars to set Env ... Not sure, if this is what you want, but
let's start somewhere :-)
mh
On Fri, Apr 6, 2012 at 8:40 PM, congo thomas wrote:
> Friends,
>
> Please, if this is obvious and thats why no one responded, please hint me.
>
> I am thinking that LD_LIBRARY_PATH might
Thanks for the replies.
We are going to use "F5" for load balancing the Tomcat instances. As
mentioned all the machines will share the same VIP.
No Apache HTTP server for now !!
I was able to use the session replication ( PersistenceManager) on tomcat
along with Apache HTTP server. I have to che
On 4/6/2012 10:34 AM, Pratapani wrote:
> Thanks for the reply.
> I have used the mod_proxy . Changed the httpd.conf to have 2 tomcat
> instances in cluster.
>
> BalancerMember ajp://127.0.0.1:8009 min=10 max=100 route=node1 loadfactor=1
> BalancerMember ajp://127.0.0.1:8019 min=20 max=200 route=no
Friends,
Please, if this is obvious and thats why no one responded, please hint me.
I am thinking that LD_LIBRARY_PATH might be a reserved word. However i
cant believe that i couldnt modify this var, per vhost.
br
congo
On Wed, March 28, 2012 09:49, congo thomas wrote:
> Any ideas on why this
Thanks for the reply.
I have used the mod_proxy . Changed the httpd.conf to have 2 tomcat
instances in cluster.
BalancerMember ajp://127.0.0.1:8009 min=10 max=100 route=node1 loadfactor=1
BalancerMember ajp://127.0.0.1:8019 min=20 max=200 route=node2 loadfactor=1
Tomcat clustering works perfect.
Hello,
after upgrading from 2.2.21 to 2.4.1 I'm seeing a problem with SNI in
combination with reverse proxying.
I have a VM with wordpress in it behind an apache reverse proxy. The
reverse proxy runs on the host system and port 12443 of this host is
forwarded into the VM and connects to 443 there
If I remove OptRenegotiate, it doesn't change anything. Behaviour is still
the same.
If I remove SSLVerifyClient, then it works fine and there is no 403 error
any more.
Best regards,
Milan