Maintaining Internal GTM POOL Connections with Active/Active Configuration

Vijay...thank you for responding back. This is one "big" application with multiple components/modules so to speak. Everything works flawlessly if one GTM pool member is disabled and all client sessions are going to the one GTM pool. Once I introduce the other GTM pool member the traffic will go between both GTM pools for one single client session when a redirect in the application occurs..... ie...opening a form for example, or signing into the application (SSO), resulting in cross datacenter traffic and timeout issues.

I need for a single client session, when accessing the application, to stay within its initial GTM Pool during the duration of the session.