Remoting, CallContext, NLB

  • Thread starter Thread starter Hawix
  • Start date Start date
H

Hawix

Our application server uses Remoting and CallContext class to assign context
data for communication with client.
We want to use network load ballancing (NLB) to scale out our architecture.
CallContext is assigned after valid execution of login method (own method of
authorization) - so, it is session.

In this case I expect problems with CallContext (when exist a more then one
application server) because requests (after login) from client can be
redirected to another application server where there is no context data.

Does anybody know how to resolve this problem in simply way?

Greattings
Hawix
 
Hi,
i'm not an expert but if i remeber corretcly, the nlb has an option to
redirect requests after the first to the same server this is called
server affinity and i think is used in web apps wheb ssl is involved.

Another approch could be to use a single db shared by the application
that contains data to rebuild CallContext based on an id of the
requestor. somehow as stata managment - option SQL - ASP.net does.
 
Back
Top