Forum Discussion
alex100_194614
Nimbostratus
NimbostratusCitrix ICA proxy session disconnect controll problem
Hi Everyone,
Quick overview of what I am trying to accomplish. To start, I have very limited experience with ICA proxy and just getting more familiar with it now. So, we have Citrix XenApp environment used for desktop application delivery for remote client. We do have a working environment(Big-IP 10.2.4 LTM, APM), however, client requested a change in application delivery configuration. Now client requested that in the event of dropped internet connection Citrix Receiver session to be disconnected on XenApp end after 60 seconds of idle time. So, I have reconfigured the timeout on backend and tested everything locally, where I was able to achieve desired result. I would launch the application and then disconnect network cable from the desktop running Citrix Receiver. As expected, the session would get dropped in XenApp console after 60 seconds exactly. Again, all of that works connecting everything directly, bypassing the Load balancer. However, when going through ICA proxy, when I pull the network cable the session does not die for 7 and a half minutes. I have tried to make changes to the TCP WaN and Lan profiles utilized by ICA proxy by changing idle timeout values to 60 seconds but all without any success. Session, would not get disconnected for 7,5 minutes no matter what I do.
Please, help me to understand why I am not able to control session timeout and what I am doing wrong. I have a suspicion that when I pull the cable, client side connection does indeed die and gets dropped, but on server side it stays alive. If that is the case I might need an iRule to kill the server side connection once client side connection dies.
Please, help me to understand...
Here is a list of default idle profile timeouts that might be useful. I would check to see if any apply to your configuration. Also, note that oneconnect will keep a connection open to reuse, try testing your configuration without oneconnect profile if it applies.
alex100_194614Ok, so after all the issue was related to Citrix. On XenApp farm, session persistence was not configured. By default it is set to 180 seconds, which was the case. Once disabled I was able to gain control over the session from LTM perspective.
