[ https://issues.apache.org/jira/browse/SVN-4641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim-Christian Bloss updated SVN-4641: ------------------------------------- Environment: Server is Debian GNU/Linux 8, Apache 2.4, using either old SVN 1.8.10 and also when cleanly upgraded to 1.9.4 (using completely newly created svn repo), supporting Kerberos authentication, x86_64. Client is Windows 2008 R2 x86_64, svn cli 1.9.4, using Kerberos authentication. Kerberos Tickets are valid for 5 minutes. Checkout takes much longer than 5 minutes. was: Server is Debian GNU/Linux 8, Apache 2.4, SVN 1.8.10 and also when cleanly upgraded to 1.9.4 (using newly created svn repo), supporting Kerberos authentication, x86_64. Client is Windows 2008 R2 x86_64, svn cli 1.9.4, using Kerberos authentication. Kerberos Tickets are valid for 5 minutes. Checkout takes much longer than 5 minutes. > silent incomplete checkout with Kerberos timeout > ------------------------------------------------ > > Key: SVN-4641 > URL: https://issues.apache.org/jira/browse/SVN-4641 > Project: Subversion > Issue Type: Bug > Components: cmdline client > Affects Versions: 1.8.8, 1.9.4 > Environment: Server is Debian GNU/Linux 8, Apache 2.4, using either > old SVN 1.8.10 and also when cleanly upgraded to 1.9.4 (using completely > newly created svn repo), supporting Kerberos authentication, x86_64. > Client is Windows 2008 R2 x86_64, svn cli 1.9.4, using Kerberos > authentication. > Kerberos Tickets are valid for 5 minutes. > Checkout takes much longer than 5 minutes. > Reporter: Tim-Christian Bloss > Labels: performance, security, windows > > When checking out by svn CLI using Kerberos tickes for authentication and > checkout takes more than 5 minutes (time that Kerberos tickets are valid), > then the checkout ends with state "success" (return code 0) but all files > which could not be fetched within the validity duration of the Kerberos > ticket are missing. > SVN also does not seem to print any warnings or information regarding this > issue we could automatically react on. > This leads to supposedly successfull checkouts but builds do fail due to > missing resources. > Example: Large maven project structure of 200+ submodules (yes we know it's > "not nice", but there's no chance to change this!), checkout takes about 15 > minutes, but after 5 minutes checkout end with state "success", but two > thirds of data volume do not get checked out, including the main pom.xml. > The same checkout using Debign GNU/Linux 8 x86_64 with cli 1.9.4 and basic > authentication works correct, checking all files out, taking the full > expected 15 minutes for the checkout. -- This message was sent by Atlassian JIRA (v6.3.4#6332)