"coreyjohnston" wrote : I could tell from the logs that the session is moved from node0 to node1. ie: the host changed to node1 but the correct session (identified by the jsessionid AND the mod_jk engine name) was able to continue running from node1. Given this, it seemed like functionally the clustering and session replication was working fine. |
Good to know, and thank you for reporting this. I need to improve my understanding of exactly what mod_jk does with the jvmRoute appended to the cookie. I'm *guessing* that it's an optimization, and not a requirement. If the jvmRoute points to a defunct server, perhaps mod_jk falls back to looking up the regular session id in a table it keeps. But this is speculation on my part. "coreyjohnston" wrote : | Also, just as an aside, I would have thought that using mod_jk and Apache as a front-end load-balancer might be quite a common setup for clustering. If this requires cookies to be used, and JBoss can't use URL rewriting in clustered mode, maybe this should be put into the nodes/wikis about clustering? Seems like a fairly significant thing. Or better yet, maybe JBoss should refuse to deploy the app? | Once I get a chance to investigate further, I'll either document the cookie requirement on the wiki (if its valid) or remove the ERROR message if the requirement isn't real. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3916221#3916221 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3916221 ------------------------------------------------------- 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
