DFS app fails in DFS WAS cluster

DFS 6.5 Sp1. .Net based application using wsdl based proxies. Application works fine with single DFS on CS (6.5 SP1). But query service fails in DFS cluster because token is not valid across machines. We need two different tokens -since the token registered at "/services/core" is not valid in the context "/services/core/QueryService". We currently get a security token using the web service proxy code. Looking for a wsdl based proxy example of how to get the token for a different service such as the query service since the token we have will not work across machines in the cluster. .NET 2.0 environment.

Thanks!

Find more posts tagged with

Comments

zhou_simonq

have you enabled sticky sessions? can you get the SOAP requests, especially the JSESSIONID in the headers, before and after the front node dispatches the task?

- simon

Brian DeWyer

yes, our understanding and WAS documentation indicates session affinity is enabled by default in WAS. We also set this to true:

NoAffinitySwitchBack Set this property to "true" to maintain affinity to the new member even after original one comes back up. When a cluster member fails, its requests routed to a different cluster member, and sessions are activated in that other member. Thus, session affinity is maintained to the new member, and when failed cluster member comes back up, the requests for sessions that were created in the original cluster member are routed back to it. Allowed values, true or false. Default: false.

We restarted the DFS JVM and cluster. Same error

zhou_simonq

As I said before, have you dumped the SOAP message, especially the JSESSIONID field in the header, to take a look at? I doubt the JSESSIONID has changed when the SOAP message passed thru the load balancer.

I'm not sure whether you can get it fixed with DFS 6.5 SP2 or even SP3, which was released couple of days ago.

- simon