Hi chwang, Mod_jk will recognize your session id request parameter only if it's called jsessionid, I suppose.
Why don't you use the 'real' HttpSession? In you servlet, you use getSession(true), this will generate a sessionId for you, and put it in a JSESSIONID cookie in the response. In the next request, you put this cookie in the request, and mod_jk will also recognize this. If your client would use commons-httpclient, this all goes automatically. HttpClient will keep all cookies, including the JSESSIONID, in a HttpState object, that you can reuse for the next request. It will even retain Credentials. Instead of mod_jk, you could also use mod_proxy_balancer from Apache 2.2. You can configure the stickysession parameter of the balancers to JSESSIONID or PHPSESSIONID, maybe others, too, or even use your own rewrite rules like in http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingMod_proxyWithJBoss Greets, Geert. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955600#3955600 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955600 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
