How is session management handled in case of a load balanced Quark Publishing Platform Server environment?

Our Technical Support Portal has changed as we have moved to a new platform. Please visit support.quark.com to access your support tickets or to log a new ticket with us. All our existing customers should look for an email from support@quark.com for activation of their New Support Account. If you face any difficulty in accessing the new portal, please write to us at support@quark.com

How is session management handled in case of a load balanced Quark Publishing Platform Server environment?

Environment: Two instances of Platform Server (say A & B) running behind a Load Balancer and Platform clients are connected to both instances through the Load Balancer.

In case of fail-over, one of the Platform server instance (say A) stops working due any reason. So, Platform clients that have sessions established with Platform Server instance A will face the problem and other Platform clients with sessions established with Platform Server instance B can continue working. Platform clients which are connected to the failed instance A need to re-login to the Platform Server to resume their work.

Note: Session replication is used in Active-Active fail-over. Quark Publishing Platform server doesn’t support Active-Active fail-over.
 
Was this answer helpful?YesNo
Topic Information
  • Topic #: 30026-3797
  • Date Created: 11/18/2015
  • Last Modified Since: 06/26/2017
  • Viewed: 19
Welcome Guest