GregTomkins
Active Member
These questions concern the simulated connections available in Session-Managed mode thru the Web Services Adapter (WSA), from the end-client running Java (or whatever) and submitting HTTP/XML/SOAP requests to the WSA. I can't find any documentation about this.
1. Is there any timeout (activity or session) in effect, or, once I get a session ID, could I literally use it for days?
2. How does WSA handle reboots, eg. if I (a Java client) get a WSA session ID and use it for an extended period of time, will it break if WSA happens to get rebooted? Or does WSA persist session ID's?
3. Similar question; how does WSA handle the possibility that I make 2 requests from the same client with the same session ID, but due to load balancing, they are directed to different WSA's?
I also sent this question to PSC Support. Any insights appreciated.
1. Is there any timeout (activity or session) in effect, or, once I get a session ID, could I literally use it for days?
2. How does WSA handle reboots, eg. if I (a Java client) get a WSA session ID and use it for an extended period of time, will it break if WSA happens to get rebooted? Or does WSA persist session ID's?
3. Similar question; how does WSA handle the possibility that I make 2 requests from the same client with the same session ID, but due to load balancing, they are directed to different WSA's?
I also sent this question to PSC Support. Any insights appreciated.