GSS issue with sticky database

[CSCO11758516]

I have configured 3 rules based on location. From location 1 to server 1, location 2 to server 2 and location 3 to server 3. When server 1 is down, traffic from location 1 moves to server 2. This is normal so far;

But when server 1 goes back online, the GSS doesn't refresh the sticky database and revert the traffic coming from location 1 to the server 1 as normal.

Could you please tell me what generate such issue?

I have compared my config with other domains and it's similar.

It's as if the GSS doesn't take care of the probing state when a sticky entry exists already for the traffic. Is there a way to activate such behavior? 

Thank you in advance.

[Aleksey Pan]

If you are using stickiness based on the IP, then yes, it is expected behavior:

1: Once the 1st server went down, the connection will go to the 2nd or 3rd server( based on what the predictor there) and then the IP addr will be saved as entry in the sticky-datatbase for that server and will be saved until there will be no connection coming from that location( Src-IP) and it will be cleared automatically after configured timeout or unless you will clear sticky-database for that answer:

From the doc:

http://www.cisco.com/c/en/us/td/docs/app_ntwk_services/data_center_app_services/gss4400series/v4-0/command/reference/GSSCMR/GenCmds.html#wp1705132

Hope this helps!