I use the EditThisCookie plugin for Chrome to specify the server behind the load balancer. The load balancer is an Apache Web Server with BalanceMember pointing to the AJP port (8009) of the uPortal server. The balancer configuration looks like this (substituting "app-server-pool" and "app-server" for our uPortal server pool and server names):
<Proxy balancer://app-server-pool>
Header add Set-Cookie "PORTAL_SERVER_ID=.%{BALANCER_WORKER_ROUTE}e; path=/" env=BALANCER_ROUTE_CHANGED
BalancerMember ajp://app-server-1:8009 route=bal1
BalancerMember ajp://app-server-2:8009 route=bal2
BalancerMember ajp://app-server-3:8009 route=bal3
BalancerMember ajp://app-server-4:8009 route=bal4
ProxySet stickysession=PORTAL_SERVER_ID
</Proxy>
In the Cookie manager, I edit the server name in PORTAL_SERVER_ID cookie (.bal1, .bal2, .bal3, .bal4) and refresh the page to test each server behind the load balancer. This has come in handy many times when users complain of intermittent errors. Usually one of the servers has a problem while the others are fine, which explains why it appears randomly.
Lauren
--
You received this message because you are subscribed to the Google Groups "uPortal Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
uportal-dev...@apereo.org.
To view this discussion on the web visit
https://groups.google.com/a/apereo.org/d/msgid/uportal-dev/358EED99-0D75-4275-9E46-B7C87E8FD7DD%40unicon.net.