One of our user is experiencing a freezing applications after being idle for more than 5 minutes. It would make a "ding" noise on the speaker as he types and the cursor does not move either (hitting tab or enter doesnt move the cursor). It's as if he was typing on the wrong line. Closing the application and relaunching it will do the trick however it would freeze again in the next 5 minutes. The application has been re-installed twice on the machine and it's still freezing. Is there anything on the settings that I can change?
Thanks in advance.
[size=1][ August 20, 2008, 06:40 AM: Message edited by: Brian T. Pence ][/size]
It sounds like he is getting locked out somehow at the host application, not from Absolute. Please answer the following...
1. Can you disconnect/reconnect rather than shutdown Absolute? If so, this means Absolute is not hung, but the host application may be.
2. Is this user using the same host application as other users? Is his environment different in any way?
3. Are keepalives enabled? (options->Properties->Connection) The only time-based thing in AbsoluteTelnet is the keepalives. It is possible the keepalives are not being interpreted properly on the host and are confusing the host application. However, the default period for keepalives is 1 minute, not 5 so I'm not sure this is the issue. Disable them anyway to see if it makes a difference.
Let me know if any of this helps (or doesn't) and we'll try to track it down further.
Brian
1. Yes. User is able to disconnect and reconnect. Reconnecting means he will have to login again and this process takes about 1-2 mins.
2. Yes the same network connection however no one else is experiencing disconnection problem.
3. Keep alive was set to 9000 seconds (15 mins), however it's still doing the same thing.
This is sounding more and more like a problem on the host end. The fact that he can disconnect/reconnect means that AbsoluteTelnet is *not* hung. The fact that it *dings* in response to a keypress means that the keypress is being sent and the server is responding with a bell. Absolute doesn't arbitrarily sound the bell itself in response to a keypress. It would be the host telling it to do so.
What version of Absolute is he using?
What terminal type?
What application is he running on the host side?
Are there any per-user configurations there that may be affecting him and nobody else?
What exactly is showing on the screen? For example, the user is interacting with the screen and then walks away, right? I assume the screen still shows the last thing he was working on. When you return 5 minutes later, is it the same thing still displayed but only responds with dings when the keys are pressed? Does the display every change at this point?
What version of Absolute is he using?
Version 5.49 winsock 2.0
What terminal type?
Telnet
What application is he running on the host side?
ISM by IBM
Are there any per-user configurations there that may be affecting him and nobody else?
No. All users have the same configuration settings.
I sent you a screenshot to your email. It seems like it's the host that rejects his key input, can you verify this information please. If this is true, I've set the idle time to 9000seconds, technically it shouldn't lock up his connection, correct?
Thank you.
Hi Brian,
The user hasn't experienced any frozen/disconnected problem with the upgrade of Absolute Telnet 6.2.8.
Thank you for all your help.
Glad to hear it!
