I searched through previous cases where this error message was reported, and found several that were resolved by making adjustments to the network connections between the broker machine and the client/agent machine. Here are a few of those:
- Resolution: After studying a few other issues where this error was debugged, it looks like a network connection gets temporarily "lost" and that's when you'll see something like this
- Resolution: The problem was resolved by installing new VPN drivers
- Resolution: Customer reported that their network team has discovered network switch issues and bandwidth problems.
- Resolution: A route change was done by customer's admins. it was reverted back and now
From case notes of one of the cases I found:
The message indicates a network issue somewhere. The first thing I would advise to double check is to ping the hostname of the agent machine from the SCM broker machine, and ping the hostname of SCM broker machine from the agent machine. Please let me know the results. Is there a firewall between the agent and the hservers?
In a couple of the cases I found recommendations to add or change the following settings in the rtclient.cm on the client/agent machine:
setopt _socket_tcp_nodelay true
setopt _conn_init_timeout 30
setopt ptm_server_accept_timeout 120
setopt ptm_client_accept_timeout 120
setopt output_warning_messages true
setopt server_keep_alive_timeout 0.0
setopt server_read_timeout 60.0 /* 30 is default */
setopt server_write_timeout 60.0 /* 30 is default */
One more idea to gather more information: You might see if the problem can be reproduced with the "hco" command line utility. If so, there is an option you can add to the command line "-tr" that will add extra tracing information to the hco.log file.
These would be some things to check on or try. If the problem persists, we could open a support case and investigate further.
Let me know if this helps.