Sun Microsystems 2005Q2 - Manual (Page 21)

▼ To Verify Load Balancing
1. To display the first page of the clusterjsp application, type this URL in your
browser:
http:// localhost:web_server_port/clusterjsp
Replace the localhost variable with the name of the system that the Web Server is
running on.
Replace the web_server_port variable with the value of the port attribute of the LS
element in web_server_install_dir/https-hostname/config/server.xml. For this
example, port 38000 is used.
A page similar to what you saw in “To Verify the Application Deployment”
on page 16 . appears.
2. Examine the Session and Host information displayed. For example:
■ Executed From Server: localhost
■ Server Port Number: 38000
■ Executed Server IP Address: 192.18.145.133
■ Session Created: Day Mon 05 14:55:34 PDT 2005
3. The Server Port Number is 38000, the Web Server’s port. The load balancer has
forwarded the request on the two instances in the cluster.
4. Using different browser software, or a browser on a different machine, create a
new session. Requests from the same browser are “sticky” and go to the same
instance.
These sessions should be distributed to the two instances in the cluster. You can
verify this by looking at the server access log files located here:
■ Solaris Java Enterprise System installation:
/var/opt/SUNWappserver/nodeagents/ nodeagent_name/i1/logs
/access/server_access_log
/var/opt/SUNWappserver/nodeagents/ nodeagent_name/i2/logs
/access/server_access_log
■ Linux Java Enterprise System installation:
/var/opt/sun/appserver/nodeagents/ nodeagent_name/i1/logs
/access/server_access_log
/var/opt/sun/appserver/nodeagents/ nodeagent_name/i2/logs
/access/server_access_log
■ Windows Java Enterprise System installation:
install-dir\nodeagents\nodeagent_name\i1\logs\access
\server_access_log
install-dir\nodeagents\nodeagent_name\i2\logs\access
\server_access_log
Steps
Chapter 1 • Quick Start 21