Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Why am I getting error message Closing socket Socket & as handler threw exception in SilkCentral Test Manager log files?

Why am I getting error message Closing socket Socket & as handler threw exception in SilkCentral Test Manager log files?

Problem:

Why am I getting error message Closing socket Socket & as handler threw exception in SilkCentral Test Manager log files?

Resolution:

These errors may be generated in your SilkCentral Test Manager log files even though tests run successfully in SilkCentral Test Manager.

This may be caused by having several servers created, but disabled; if you completely remove the servers then these errors may no longer occur. The errors may occur because SilkCentral is checking the servers even though they are disabled, the fact that the tests still run successfully means that this is not affecting the executions and this is simply a part of the execution as SilkCentral checks all defined servers.


Old KB# 24993

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 19:51
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.