tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Artur <ar...@upi.pl>
Subject Mod_jk balancing, session problem
Date Tue, 08 Aug 2006 14:37:03 GMT

Hello,

We have environment with Apache (2.2.0) + Tomcat (5.5.17) connected via
mod_jk (1.2.18). Further tomcat makes some queries to databese through
Tuxedo services (BEA).
Everything works fine until heavy load when something stops responding
(Service not available).
We think it is tomcat or mod_jk. It occures when "Max busy connections" on
mod_jk status manager shows about 200. Mod_jk is in error status then.

So we decided to use mod_jk load balancing feature and we installed another
instance of tomcat (on the same machine).
Now service is available even under heavy load but we are losing sessions.
Of course sticky_session is set to "true".
Below I paste our config files. Please help if you only can.

Best regards
Artur

###Jk status for one day:

Name	Type	jvmRoute	Host	Addr	Stat	D	F	M	V	Acc	Err	Wr	Rd	Busy	Max	RR	Cd
worker2	ajp13	worker2	localhost:8009	127.0.0.1:8009	OK	0	1	1	2144	824825	512
480M	5.8G	6	138	worker3

###httpd.mpm section:
# worker MPM
# StartServers: initial number of server processes to start
# MaxClients: maximum number of simultaneous client connections
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxRequestsPerChild: maximum number of requests a server process serves

<IfModule mpm_worker_module>
    StartServers         5
    MaxClients           448
    MinSpareThreads      5
    MaxSpareThreads      25 
    ThreadsPerChild      7
    MaxRequestsPerChild   0
</IfModule>

###workers.properties:
# Define 3 workers, 2 real workers using ajp13 and the last one being a
loadbalancing worker

  worker.list=worker1,jkstatus

# Set properties for worker2 (ajp13)
  worker.worker2.type=ajp13
  worker.worker2.host=localhost
  worker.worker2.port=8009
  worker.worker2.lbfactor=1
  worker.worker2.connection_pool_size=7
  worker.worker2.connection_pool_timeout=300
  worker.worker2.socket_timeout=60

  # Set properties for worker4 (lb) which use worker1 and worker2

  worker.worker3.type=ajp13
  worker.worker3.host=localhost
  worker.worker3.port=8019
  worker.worker3.lbfactor=1
  worker.worker3.connection_pool_size=7
  worker.worker3.connection_pool_timeout=300
  worker.worker3.socket_timeout=60


# Define a 'jkstatus' worker using status
  worker.jkstatus.type=status

  worker.worker1.type=lb
  worker.worker1.sticky_session=true
  worker.worker1.method=R
  worker.worker1.balance_workers=worker2,worker3


###server1.xml - connector section:
<!-- Define an AJP 1.3 Connector on port 8009 -->
    <Connector port="8009" 
               enableLookups="false" redirectPort="8443" protocol="AJP/1.3"
/>

    <Engine name="Catalina" defaultHost="localhost" jvmRoute="worker2">


###server2.xml - connector section
<!-- Define an AJP 1.3 Connector on port 8009 -->
 

   <Connector port="8019" 
               enableLookups="false" redirectPort="8443" protocol="AJP/1.3"
/>

    <Engine name="Catalina" defaultHost="localhost" jvmRoute="worker3">






-- 
View this message in context: http://www.nabble.com/Mod_jk-balancing%2C-session-problem-tf2073073.html#a5707787
Sent from the Tomcat - User forum at Nabble.com.


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message