View Single Post
  #1  
Old 13th June 2012, 09:41
jeyintel jeyintel is offline
Junior Member
 
Join Date: Jun 2012
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default Ubuntu+windows apache+tomcat Configuration

Hi,

I want to configure apache+tomcat loadbalancing using JK connector.This works in full windows/linux environment.But in hybrid environment I am little bit confused.The schenario below.

1.Http server - Ubuntu 12 server 12.04
2.two tomcat 5.0.34 will be there in two windows server 2008.

3.my worker.properties below.
# workers.properties -
#
# This file is a simplified version of the workers.properties supplied
# with the upstream sources. The jni inprocess worker (not build in the
# debian package) section and the ajp12 (deprecated) section are removed.
#
# As a general note, the characters $( and ) are used internally to define
# macros. Do not use them in your own configuration!!!
#
# Whenever you see a set of lines such as:
# x=value
# y=$(x)\something
#
# the final value for y will be value\something
#
# Normaly all you will need to do is un-comment and modify the first three
# properties, i.e. workers.tomcat_home, workers.java_home and ps.
# Most of the configuration is derived from these.
#
# When you are done updating workers.tomcat_home, workers.java_home and ps
# you should have 3 workers configured:
#
# - An ajp13 worker that connects to localhost:8009
# - A load balancer worker
#
#

# OPTIONS ( very important for jni mode )

#
# workers.tomcat_home should point to the location where you
# installed tomcat. This is where you have your conf, webapps and lib
# directories.
#
#workers.tomcat_home=/usr/share/tomcat6
workers.tomcat_home=/tomcatA

#
# workers.java_home should point to your Java installation. Normally
# you should have a bin and lib directories beneath it.
#
#workers.java_home=/usr/lib/jvm/default-java
workers.java_home=$JAVA_HOME

#
# You should configure your environment slash... ps=\ on NT and / on UNIX
# and maybe something different elsewhere.
#
ps=/

#
#------ ADVANCED MODE ------------------------------------------------
#---------------------------------------------------------------------
#

#
#------ worker list ------------------------------------------
#---------------------------------------------------------------------
#
#
# The workers that your plugins should create and work with
#
#worker.list=ajp13_worker
worker.list=tomcatA,tomcatB,loadbalancer

#
#------ ajp13_worker WORKER DEFINITION ------------------------------
#---------------------------------------------------------------------
#

#
# Defining a worker named ajp13_worker and of type ajp13
# Note that the name and the type do not have to match.
#
#worker.ajp13_worker.port=8009
#worker.ajp13_worker.host=localhost
#worker.ajp13_worker.type=ajp13

worker.tomcatA.port=8009
worker.tomcatA.host=10.50.9.246
worker.tomcatA.type=ajp13
worker.tomcatA.lbfactor=1

worker.tomcatB.port=8009
worker.tomcatB.host=10.50.9.247
worker.tomcatB.type=ajp13
worker.tomcatB.lbfactor=1
#
# Specifies the load balance factor when used with
# a load balancing worker.
# Note:
# ----> lbfactor must be > 0
# ----> Low lbfactor means less work done by the worker.
#worker.ajp13_worker.lbfactor=1

#
# Specify the size of the open connection cache.
#worker.ajp13_worker.cachesize

#
#------ DEFAULT LOAD BALANCER WORKER DEFINITION ----------------------
#---------------------------------------------------------------------
#

#
# The loadbalancer (type lb) workers perform wighted round-robin
# load balancing with sticky sessions.
# Note:
# ----> If a worker dies, the load balancer will check its state
# once in a while. Until then all work is redirected to peer
# workers.
#worker.loadbalancer.type=lb
#worker.loadbalancer.balance_workers=ajp13_worker
worker.loadbalancer.type=lb
worker.loadbalancer.balanced_workers=tomcatA,tomca tB
worker.loadbalancer.sticky_session=1


Please guide to implement.
Reply With Quote
Sponsored Links