-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
SIT Environment
Hi I am using TFS as my source repository and configured Jenkins with TFS for moving automated builds for every check-In and it was working fine for more than a month.
But now I have ran into below error where I am not finding any solution please help me on this.
Error Message:
[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Done
FATAL: null
java.lang.StackOverflowError
at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListenerList.java:304)
at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListenerList.java:304)
at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListenerList.java:304)
at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListenerList.java:304)
at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListenerList.java:304)
Currently my Versions are :
Team Foundation Server Plug-In version is 5.126.0
Jenkins - 2.89.4
I have also tried restarting my slave services on windows server and restarted my windows server but it didn't fix my issue.
Please help me on this.
Thanks in Advance . Really appreciate your Time and Support .
- is related to
-
-
- Open
-
-
-
- Open
-
[JENKINS-50331] JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
g Tilak
created issue -
We're having this problem for the latest TFS plugin versions, too. This needs urgent fix since when we get this error, all of the jobs start to fail until a Jenkins restart. Restarting Jenkins solves the issue temporarily until it happens again (usually in 24 hours). We are using up to date Jenkins and TFS Plugin versions. --> Currently, Jenkins: v2.121.2 / TFS Plugin: v5.139.2
We had this issue before with Jenkins v2.60.1 + TFS Plugin: v5.139.1 before we upgraded our Jenkins setup to the latest version.
I can confirm that TFS Plugin v5.121.0 doesn't have this bug. So we downgraded to this version. However it has its own bugs :/
Murat Gundogdu
added a comment - - edited We're having this problem for the latest TFS plugin versions, too. This needs urgent fix since when we get this error, all of the jobs start to fail until a Jenkins restart. Restarting Jenkins solves the issue temporarily until it happens again (usually in 24 hours). We are using up to date Jenkins and TFS Plugin versions. --> Currently, Jenkins: v2.121.2 / TFS Plugin: v5.139.2
We had this issue before with Jenkins v2.60.1 + TFS Plugin: v5.139.1 before we upgraded our Jenkins setup to the latest version.
I can confirm that TFS Plugin v5.121.0 doesn't have this bug. So we downgraded to this version. However it has its own bugs :/
Allan BURDAJEWICZ
added a comment - 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
Allan BURDAJEWICZ
added a comment - 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
Jatin Bedi
added a comment - +1.
Any updates on this would be appreciated. | Assignee | Original: redsolo [ redsolo ] | New: Jason Prickett [ jpricketmsft ] |
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
Allan BURDAJEWICZ
added a comment - - edited 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 
I am also facing same issue. However in my case restarting the Jenkins service fixed it temporarily. But I need a more permanent solution, I cannot restart Jenkins service whenever we face this issue. Is there something have you done to fix it?