Looks like I figured out what was going on. There seems to be a bug in the
Tomcat implementation where it attaches the ClusteredSingleSignOn to the wrong
< Host >. I had:
< Engine name="jboss.web" defaultHost="A" >
...
< Host name="A" jvmRoute="node1" ... >
< Alias >localhost< /Alias >
]]
like the Tomcat documentation states. However, doing this caused all the
valves defined in this to be attached to a Host w/ name="localhost" (which
isn't defined anywhere in my server.xml file), and the Host w/ name=A" didn't
have any valves attached to it.
The clue was that I wasn't seeing a JSESSIONSSO cookie being set after login to
the server.
When I switched over to
< Engine name="jboss.web" defaultHost="localhost" >
...
< Host name="localhost" jvmRoute="node1" ... >
< Alias >A< /Alias >
it worked just fine, and the JSESSIONSSO became set.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3879356#3879356
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3879356
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
