Hmm, interesting. I based my comment about the requirement for cookies on the
following bit from the JvmRouteValve's checkJvmRoute() method:
// Check if incoming session id has JvmRoute appended. If not, append it.
| // TODO. We handle only get session id by cookie only
| if (req.isRequestedSessionIdFromURL())
| {
| // Warning but do nothing
| log_.error("JvmRoutValve.checkJvmRoute(): Can't handle
clustering where session id is from URL. Will skip.");
| }
| else
| {
| handleJvmRoute(sessionId, jvmRoute, res);
| }
Did you have any ERROR messages in your logs? Besides ERROR messages in the
logs, this would only surface as a problem if a session failover occured.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916217#3916217
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916217
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user