[JENKINS-18747] Checkouts from Subversion 1.7 server fail

I recently started migrating my projects from a subversion 1.6 server to a 1.7.9 server. Both use dav_svn through Apache. Since then, about 1 out of every 3 builds will fail with a "connection timed out" stack trace from the SVN plugin. This is happening with multiple projects, usually when getting an external. The new server should be substantially more performant than the old one, and is on a much faster network. If I move all the SCM tasks into scripts and use a "real" SVN 1.7 client, everything works reliably. Additionally, all my users have no trouble using the new server. Only Jenkins is failing. Full trace attached.

---
Originally reported by qhartman, imported from: Checkouts from Subversion 1.7 server fail

• status: Open
  
• priority: Major
  
• component(s): subversion-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 20251212-090250
  

Raw content of original issue

I recently started migrating my projects from a subversion 1.6 server to a 1.7.9 server. Both use dav_svn through Apache. Since then, about 1 out of every 3 builds will fail with a "connection timed out" stack trace from the SVN plugin. This is happening with multiple projects, usually when getting an external. The new server should be substantially more performant than the old one, and is on a much faster network. If I move all the SCM tasks into scripts and use a "real" SVN 1.7 client, everything works reliably. Additionally, all my users have no trouble using the new server. Only Jenkins is failing. Full trace attached.

1 attachment

- [svn_trace.txt](https://issues.jenkins.io/secure/attachment/23925/svn_trace.txt)