My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 3697: Setting receive.maxObjectSizeLimit causes 'Too many concurrent connections' error
1 person starred this issue and may be notified of changes. Back to list
Status:  AwaitingInformation
Owner:  ----


Sign in to add a comment
 
Reported by anantha....@gmail.com, Nov 25, 2015
*****************************************************************
*****                                                       *****
***** !!!! THIS BUG TRACKER IS FOR GERRIT CODE REVIEW !!!!  *****
*****                                                       *****
***** DO NOT SUBMIT BUGS FOR CHROME, ANDROID, CYANOGENMOD,  *****
***** INTERNAL ISSUES WITH YOUR COMPANY'S GERRIT SETUP, ETC.*****
*****                                                       *****
*****   THOSE ISSUES BELONG IN DIFFERENT ISSUE TRACKERS     *****
*****                                                       *****
*****************************************************************

Affected Version: 2.11.2

What steps will reproduce the problem?

I am using Gerrit 2.11.2 on Tomcat 7.0.47 on Windows 7.

I am trying to restrict the size of files that could be pushed to Gerrit with receive.maxObjectSizeLimit in gerrit.config. This works as expected blocking the git push with an appropriate error.
However, after this failed push, all git operations [except local operations like git commit, git status and git log.. etc.,] fail with

Received disconnect from <<gerrit IP>>: Too many concurrent connections
fatal: Could not read from remote repository.

This is pretty much consistently reproducible after a big file is blocked. To overcome this, I had to set sshd.maxConnectionsPerUser to 0. Which solved the problem, but I am not happy why a blocked push should cause 'Too many concurrent connections' error? I think it's a bug. Please let me know your thoughts on this.



What is the expected output? What do you see instead?
Setting receive.maxObjectSizeLimit should not have any adverse effects.

Please provide any additional information below.

Dec 8, 2015
Project Member #1 dougk....@gmail.com
Interesting.  Could this in fact be a duplicate of Issue 3685? (To check, with another user, you can run the "gerrit show-connections" SSH command to see how many connections there are per user.)  You are correct, sshd.maxConnectionsPerUser should control "too many concurrent connections" -- but my thought is when a push is rejected because it exceeds the object size limit, perhaps that causes an immediate connection to leak.
Status: AwaitingInformation
Dec 11, 2015
#2 anantha....@gmail.com
Hello Doug,

For some reason I am unable to reproduce the issue. Hence can not check 'gerrit show-connections'.

Could you please keep the issue open for a week at least?

Regards,
Anantha
Sign in to add a comment

Powered by Google Project Hosting