View Single Post
  #1 (permalink)  
Old August 9th, 2008, 01:05
LenDB2 LenDB2 is offline
Junior Member
 
Join Date: Jul 2008
Posts: 5
Groans: 0
Groaned at 0 Times in 0 Posts
Thanks: 0
Thanked 0 Times in 0 Posts
Rep Power: 0
LenDB2 is on a distinguished road
Smile Scalability not working as advertised/expected

Hello OTM'ers!
- My customer is testing on 5.5 CU4. Application and Web Servers all running on Sun Solaris 9 (64-bit).

- Configuration is 2 web server processes (Apache/Tomcat) and 2 Application Servers processes (Default and App99).

- Defined a single DEFAULT cluster, made up of both Application Servers (Default and App99) with equal weights of 1.

- This is an active-active configuration (Failover box is NOT checked for either App Server).

- No function based routing, No Domain based routing, etc. Plain vanilla, with expectation that ALL work gets routed to all App Servers (Scalability Topology).

- Integration is using SOAP WSDL directly to App Server (Default Server), bypassing web servers altogether (NO HTTP POST or AQ being used).

- Admin panels confirm the configuration and all check marks indicate everything is working as designed.

- Scalability Guide (June 200 indicates this single default cluster with multiple app servers (and no explicit routing) should result in all work being routed to all App Servers in the cluster.

- Over 5,000 orders "pumped" (via Integration) in a short period of time.

- Unfortunately, Default Server is handling ALL activity. None of the work (read: Zero) is being processed by the second App Server (APP99) in the Default Cluster.


Any insight/assistance would be greatly appreciated.

Thanks!
LenDB2
Reply With Quote