I have operators that stay on my workstations 24/7/365. Assuming there are no other problems, they get kicked off of their View sessions after about 24 days. We are using HP Thin Clients running the ThinOS and VMware View Client. When I check the debug log on the Windows 7 VM I see that when the connection is established, it writes the following line:
2014-09-09 08:44:30,807 DEBUG <MessageFrameWorkDispatch> [wsnm_desktop] sessionDisconnectTimer: Setting timer for 2147480 seconds
After time expires, I get the following messages in the same log and the client disconnects:
2014-09-09 08:30:08,571 DEBUG <TimerService> [wsnm_desktop] sessionDisconnectTimer: timer triggered, disconnecting session.
2014-09-09 08:30:08,571 DEBUG <TimerService> [wsnm_desktop] session::SessionDisconnectTimedOut: Disconnect message posted to desktop
Where is it getting this timer from? The global setting on the View server is maxed out at 9,999,999 minutes.
Host is EXSi 5.0.0
VMware View Server is 5.0.0-481677
View Agent 5.0.1
OS is Windows 7 Pro running on VM version 7
This is a known issue that has been fixed in View 5.3.2 - the global timeout in minutes is converted to a time in milliseconds, which is then overflowing a 32-bit counter. See VMware Horizon View Release Notes
A desktop session will timeout and be disconnected after about 24 days, 20 hours and 31 minutes even though the Session timeout setting has been set to a larger value.
Mike
This is a known issue that has been fixed in View 5.3.2 - the global timeout in minutes is converted to a time in milliseconds, which is then overflowing a 32-bit counter. See VMware Horizon View Release Notes
A desktop session will timeout and be disconnected after about 24 days, 20 hours and 31 minutes even though the Session timeout setting has been set to a larger value.
Mike
