Bitbucket bult-in SSH server stop work after 3-4 days uptime

[Sergey Subbotin]

after Bitbucket server upgrading from 6.8 to 7.6, the built-in SSH server began to fall every few days, that is, at some point the server stops responding to SSH requests to repositories, stops writing logs to the atlassian-bitbucket.log.
At the same time, the resources of the system work correctly and do not show the causes of problems.
The only thing we noticed is that network connections on port 7999 are clogged.

from the information that I have:
The problem of network connections is not regulated by the system in any way, and what should be looked at on the side of the application using this port.

[Todd Krzeminski]

Was there ever a resolution to this issue in subsequent releases? 

[Sergey Subbotin]

we are still experiencing this problem, we provided thread dumps, jmx memory, and support zip, opened a ticket with Atlassians, is still open

do you have a similar problem?

our version :Atlassian Bitbucket server 7.8.0

[Todd Krzeminski]

Not with SSH. We're on 7.6, and we're losing connectivity to our MSSQL server. Everything looks OK on the SQL side, so I was wondering if there was a known issue with Bitbucket. We see this occurring daily, so it's a bit more frustrating.

[Vimalraj Periyasamy]

@Sergey Subbotin Have you got some solution for this issue?

[Sergey Subbotin]

we disabled integration with upsource, after this crashes stopped

[Vimalraj Periyasamy]

Great.! What exactly upsource means?  Did you get answer for your ticket?

[Sergey Subbotin]

Upsource is a smart code review tool and a repository browser that supports Git.

My guess is that he was opening too many ssh connections at the same time. It was his disabling that helped us stop the endless falls of the bitbucket

Disabling Upsource is answer to my question.

[Vimalraj Periyasamy]

But opening too many SSH connection shouldn't cause this problem. Do we have limit for SSH connections? Can we increase it somehow?

[Sergey Subbotin]

I can't explain it any other way. It was a very long time ago and was repeated on all versions from which it appeared, until the service I specified was turned off.

it was the into bitbucket ssh server that crashed and there was a long correspondence with support, which could not help in any way, a support ticket was maintained for a year and a half and ended in nothing.

[Vimalraj Periyasamy]

Thanks for quick response :-)