There are some clue about how to fix this in https://social.msdn.microsoft.com/Forums/vstudio/en-US/2ace3851-8e1c-4aee-8e2d-192b0810213a/tfs-sdk-leak?forum=tee

Is there an update on this issue? It looks like a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-35432.

It was also observed on a Jenkins 2.138.3 with TFS Plugin 5.142.0.

It looks like the link shared by Allan might be helpful to cook a fix.

I am seeing this issue too. An update would be appreciated.

Environment where this issue is observed:

Jenkins 2.164.3
TFS Plug-in: 5.133.0

+1.

Any updates on this would be appreciated.

jpricketmsft I assigned this ticket to you because you've made sone of the most recent commits to this plugin, whereas the 'redsolo' user this was assigned to has not been active in this Jira instance since 2014. I hope that's OK. If you or one of the other current maintainers of the plugin should be made the default assignee for new issues, let me know and I can change that setting.

CloudBees Support has received a case from a customer who is affected by this bug, so I was hoping to get some attention on it, since we do not maintain this plugin.

I also found http://blogs.pitx3.com/2016/01/24/mulesoft-microsoft-java-tfs-stackoverflowerror. This user has reached out to Microsoft and while they did not confirm it was a bug they provided him with a workaround.

It is mentioned in the release note that Stackoverlflow issue is solved in https://github.com/microsoft/team-explorer-everywhere/releases/tag/v14.0.3. If we have a look at the source code of the SDK) however, the TFSConfigurationServer is closed after the TFSTeamProjectCollection and (while the workaround is to close it before).

We can see that the TFS plugin does already this in a way. But there is some legacy code using reflection that could be cleaned up. Proposed https://github.com/jenkinsci/tfs-plugin/pull/230

kelliejos leantk bbenz I just wanted to ping a few of you since you all seem to be recent contributors to this plugin. At CloudBees, we have a couple of customers who have been affected by the issue described here, and they are forced to restart Jenkins regularly to work around it. We have proposed this PR as a possible solution: https://github.com/jenkinsci/tfs-plugin/pull/230 If there is anything else we can do to work with you on this, please let us know!

I have also proposed https://github.com/jenkinsci/tfs-plugin/pull/233 to deal with potentially unclosed connections.

In JENKINS-58030, oli_at_jsi, mentioned dastahel is now responsible for the plugin. Mentioning to see if that provides traction.

Have not seen any real action on the plugin since 2018-07, which is just before MS bought GitHub. Wonder if they've just abandoned support for TFS?

Any word or updates to this issue?  This overflow error happens to us frequently, and people are getting angry that we keep having to restart the Jenkins server in the middle of the day to get things back up and running.  Thanks!