On Mon, Sep 22, 2008 at 1:45 AM, Shaun Senecal <[EMAIL PROTECTED]> wrote:
> Are you using the ClusterSingleSignOn Valve?
I'm not, no.
I have httpd 2.2 on the front-end, with a balancer pool thus:
ProxyRequests Off
ProxyVia Off
ProxyPreserveHost On
ProxyErrorOverride On
ProxyTimeout 60
<Proxy balancer://tomcat>
BalancerMember ajp://10.1.1.231:8009 min=10 max=50
BalancerMember ajp://10.1.1.232:8009 min=10 max=50
#BalancerMember ajp://10.1.1.233:8009 min=10 max=50
Order deny,allow
Allow from all
</Proxy>
ProxyPass / balancer://tomcat/ lbmethod=byrequests
stickysession=JSESSIONID nofailover=On
ProxyPass /servlet balancer://tomcat/servlet
lbmethod=byrequests stickysession=JSESSIONID nofailover=On
ProxyPass /piston balancer://tomcat/piston
lbmethod=byrequests stickysession=JSESSIONID nofailover=On
ProxyPass /manager balancer://tomcat/manager
lbmethod=byrequests stickysession=JSESSIONID nofailover=On
ProxyPass /link balancer://tomcat/link
lbmethod=byrequests stickysession=JSESSIONID nofailover=On
ProxyPass /ajax balancer://tomcat/ajax
lbmethod=byrequests stickysession=JSESSIONID nofailover=On
When I browse to the login page, I see a jsessionid in firebug. I
login, the jessionid cookie stays the same. I try to navigate within
the application, and wherever I click I end up on the login screen
again, with the message "user has timed out". The cookie doesn't
change until I login, in which case I see a new cookie.
If I comment out two of the BalancerMembers, the app works fine. If I
add one in (as above) I get the same behaviour.
>From reading the archives, it seems I should set a route in httpd.conf
snippet and a jvmroute in the engine tag for each tomcat server.xml.
I'll try this shortly, but it seems as if Richard did this, but still
experienced problems.
Thanks,
S.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
