Persistence state changes in Load balancing method.
guys i have one issue.
A script is been used to the functionality of an applictaion where there users will login from those 4 different client machines and the client sends request every 10 secs. Persistence timeout set to 300 secs, tcp idle time out is 300 secs. OneConnect profile disabled. Load balancing set to least session and persistence is Source Address Affinity at least on this setting it works as expected some time but after 15-20 mins problem appears client state is changed.
have you people encounter such problem before? please let know. For sure persistence/tcp idle timeout is not expired and the pool members never went up/down. so what can be the cause?
Thu Feb 26 10:15:28 GMT 2019 Sys::Persistent Connections
source-address - 10.10.1.100:443 - 172.16.10.101:443
TMM 1 Mode source-address Value 192.168.10.100 Age (sec.) 1 Virtual Name /Common/Testing_VS Virtual Addr 10.10.1.100:443 Node Addr 172.16.10.101:443 Pool Name /Common/Testing_Pool Client Addr 192.168.10.100 Local entry
Thu Feb 26 10:15:40 GMT 2019 Sys::Persistent Connections
source-address - 10.10.1.100:443 - 172.16.10.102:443 ------------> client connected different pool member
TMM 1 Mode source-address Value 192.168.10.100 Age (sec.) 1 Virtual Name /Common/Testing_VS Virtual Addr 10.10.1.100:443 Node Addr 172.16.10.102:443 Pool Name /Common/Testing_Pool Client Addr 192.168.10.100
Local entry