login about faq

I am running sftpg3.exe in batch mode in an automated fashion through out the day. I am experiencing a problem where on off my connections get stuck and all subsequent connections to that IP address are blocked because the connection broker is stuck on the old conenction. The only way that I know to solve this problem is to manually kill the connection broker process using the task manager. This has the side affect of killing any other connections that don't need to be killed.

Is there a way to timeout the connection broker? I'm not really sure what the problem is other than the connection gets stuck. It seems to be a networking issue because after restarting the broker the same connection/ip works fine.

I am using version 6.0 of the client and broker.

asked Jun 05 '12 at 21:30

jeff%20lee's gravatar image

jeff lee


I recommend you upgrade to the latest SSH Tectia version, because there was performance and stability fixes done after the 6.0 version that sound similar to your issue.

Regards, -Joe


answered Jun 15 '12 at 01:29

Joe%20-%20Tectia%20Support's gravatar image

Joe - Tectia Support ♦♦

get connection id then close it. A. get connection id (on this case it's 101) ssh-broker-ctl -a /tmp/ssh-sshmft/ssh-broker list-connections

  1. port 22 as remote_user [CONNECTING] Open since Mon 09 Jul 2012 02:03:38 PM PST [up 00:00:00] No open channels.

B. Close connection ssh-broker-ctl -a /tmp/ssh-sshmft/ssh-broker close_connection <connection_id> ssh-broker-ctl -a /tmp/ssh-sshmft/ssh-broker close_connection 101


answered Jul 09 '12 at 09:11

mftuser's gravatar image


edited Jul 09 '12 at 09:13

Sadly, I tried this already. The connection broker refuses to perform any actions other than list-connections. Since there are no channels open I cant use that command. The close connection command doesn't actually close the connection for me. I suspect that it has to do with the fact that the connection has been open for 2 days. The broker thinks the connection is still open but the connection is really gone. However the broker will not make subsequent connections while waiting for the existing connection to terminate.

Killing the broker process seems to be the only action that corrects the problem.


answered Jul 09 '12 at 20:43

jeff%20lee's gravatar image

jeff lee

Hi Jeff,

I have encountered a similar scenario when we were running an older version and restarting the process clears everything. We are now using and so far we are not seeing this


answered Jul 10 '12 at 03:30

mftuser's gravatar image


Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Jun 05 '12 at 21:30

Seen: 7,434 times

Last updated: Jul 10 '12 at 03:30

All user contributed content licensed under the cc-by-sa license.
Powered by OSQA.