AltocumulusWe have a tcp app that creates a connection to a pool member that won't break when a priority group gets deactivated. I have tried several different irules using LB_SELECT and CLIENT_ACCEPTED entry points with no luck. I need to find a spot which I can identify the ongoing TCP connection in an iRule -- then reject it so a new transaction gets load balanced to the proper priority group.
Thanks,
Frank
The question begs, why would you want to terminate a perfectly good connection? Priority groups work this way by design - to allow existing connections to pool members that are no longer part of an "active" priority group to complete normally. New connections to those "deactivated" pool members are not allowed. Is there a specific reason why you want to terminate these connections before they complete normally? Or is this a problem that the connection never terminates normally?
Check out the iRule I wrote earlier in this post. It should give you a good starting point.
AltocumulusSorry thought I asnwered this yesterday, but do not see my reply. We need the long running transaction to go to the primary server when it becomes available, otherwise we have a processes running on to different servers.
