how many times can you spot the letter o in:
q: how to find limits of clustered tomcat with session replication i am working on a tomcat cluster experimentally because of it may be need for us production environments. it must be scaleable, high available and support as much as multi concurrent users. because of that i made a test environment like that:
           haproxy
           /     \
          /       \
tomcat 1 (7.0)  tomcat 2(7.0)
  redis 1         redis 2

tomcats are load balanced on haproxy and they replicated their sessions via redis. every redis connected each others via sentinel. finally every tomcat and redis bundles are a machine. for example, tomcat 1 and redis 1 are on same server.
at the end of this experiment lab i have some questions,


*

*how can i push the limits of this lab? i tried to basic applications on tomcat but i need to know limits of this cluster to discover potential failover points.

*what are potential weaknesses of this lab? what is the best practices on same issues?

*what is advantages or disadvanteges of using web logic or wildfly instead of tomcat or using tomcats default deltamanager or backupmanager?

*i want to try replicate node memories to each other. is it possible? if possible, i want to know your recommendations :)


thanks in advance.

a: you need to focus on your application testing, not the tomcat (or whatever application server) testing. 
the process of discovering the breaking point of the system under test is known as stress testing, the idea is the following:


*

*using a load testing tool create a workload which will represent normal application usage scenario(s) 

*set up monitoring of baseline health metrics of the jvm where tomcat is running and underlying operating system.   

*start with 1 virtual user and gradually increase the load at the same time keeping an eye on system resources consumption. 

*when any of system resource consumption metrics (cpu, ram, network/disk io) will exceed, i.e. 90% of maximum available capacity or system will start swapping or jvm will perform garbage collections to often or application response time will start exceeding acceptable threshold levels or errors will start occurring - this is so called bottleneck and this is how many concurrent users (or requests per second) your application is able to serve. 


user
There are 140 "o"s in the text you provided.
assistant