Hi Josef, Thanks for your time and reply.
Yes I read about scope="soapsession", currently we are using scope="application". There are multiple reasons why we are using "application" and why we cannot change it to "soapsession" 1. Server initialization takes pretty long time as it has to collect lots of data as part of the initialization. 2. Server bootstrap is done as part of initialization, so bootstrap is called only once since we are using application scope. 3. For internal sessions we time out based on idle time for which we run our own configurable counters. 4. Once session is timed out, server throws exception and client has to reset the context(our internal thing) to server(note: we still use same connection though, it is just internal time out and reset) 4. Already many partners have implemented server implementation and we cannot afford to change it. 5. Apart from this(cookie overwriting) issue, everything else works perfectly fine for us using application scope. Basically, touching anything in server side is not in our hands except for few configuration settings. So please let me know if you think of any solution which can be done in client side. As I have also mentioned in the description, does persisting these cookies in client side and setting them in MessageContext property for each request helps? Thanks, Santhosh -- View this message in context: http://axis.8716.n7.nabble.com/Cookie-getting-overwritten-when-client-connects-to-multiple-servers-tp111918p111926.html Sent from the Axis Java - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org
