All: Have an interesting issue. We have an application that was deployed prior to my arrival to the company. When the application was first deployed the admins left cookies=true enabled in server.xml. Our applications are primarily used by phones/wap devices. These devices store their cookies on the cell providers WAP Gateway. I've been tasked with getting these applications load-balanced. I've accomplished this on most applications by setting jvmRoute in server.xml and configuring our load-balancers to pick up this string.
Here's the interesting part of the equation. Somehow I have to force the tomcat engine to disregard the cookie sent by the phone and force the engine to establish a jsessionid and pass this back to the wap device. I've turned off the cookies in the engine. Has anyone else encountered this? Any tips on an engine configuration that will force tomcat to set a sessionid despite getting a cookie from the app? Thanks, Kris-- Kris Briscoe Sr. UNIX Engineer "Unix is very simple, but it takes a genius to understand the simplicity"
