vms process left in com state

February 8, 2011 at 14:26:54
Specs: Windows XP
We are running Open VMS v7.32 on a twin Alpha cluster. The user application is written in Synergy v9. Users connect to the system via legacy LAT DECservers & dumb terminals or via windows PCs using Reflection terminal emulation with a Telnet session.
There is no problem with the DECservers but several times a day a Telnet session is abruptly ended leaving the Synergy process running in a COM state, using a vast amount of cpu time. The only way out is to stop the process.
Has anyone met this situation with Synergy / VMS and has any advice or solutions?

See More: vms process left in com state

Report •

February 9, 2011 at 10:50:19
We encountered a similar problem on VAX. We reduced it by setting a "keepalive-timer" on the telnet service.

We use the Multinet TCP stack, which has a default keepalive-timer on telnet of over 2 hours. We changed it to be a few minutes.

Check the documention for your TCP stack. The concept is probably similar for all of them.


Report •

May 1, 2012 at 04:53:27
If this problem has not yet been resolved, further niformation would be required to determine the cause. This can be an application problem that is not handling the disconnect properly. If this happens again, use analyze/system and examine the process. Gather some PC information and see where the "loop" is happening. If you can not accomplish this on your own, send me an Email and I'll provide additional information and steps.


Report •
Related Solutions

Ask Question