[
https://issues.apache.org/jira/browse/SVN-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Zhakov resolved SVN-2128.
------------------------------
Resolution: Cannot Reproduce
Fix Version/s: (was: unscheduled)
Closing as 'Cannot Reproduce': no reproduction script, no prior discussion on
mailing list.
> svnserve slows down / stops file sharing on Win2003
> ---------------------------------------------------
>
> Key: SVN-2128
> URL: https://issues.apache.org/jira/browse/SVN-2128
> Project: Subversion
> Issue Type: Bug
> Components: svnserve
> Affects Versions: 1.1.x
> Environment: Windows 2000
> Reporter: Subversion Importer
> Priority: Blocker
>
> This is filed under Windows 2000 because there was no option for 2003 Server.
> I've had SVN installed for about a week, and have been running svnserve as a
> service (damon) process on Win2k3. 3 times now the server has basically
> slowed all file sharing connections to a hault; no explaination as to why.
> The first two times I fixed it with a server reboot; this last time on a
> hunch I tried unloading svnserve and immediately the server started
> responding well again. I was using the default svnserve port, and there is
> not anything special with the network setup -- two NICs, one public, one
> private with NAT routing and VPN access enabled.
> Normally QuickBooks can load data off the file share in a matter of 10
> seconds, when this issue appears, it takes well over 10 minutes to load the
> same data. Likewise, our outlook PST files are stored on the file share; and
> normally changing between emails in outlook is instantaneous. When this
> slowdown occurs, Outlook either locks up or takes 30+ seconds just to show
> the newly selected email.
> I've seen something similar with Snom server software for VoIP systems. Both
> on one of our XP test machines and a client Windows 2000 server, the file
> sharing was knocked offline intermittantly. We never found what the solution
> for it was; however the software was also designed for unix enviroments first
> and then ported to Windows. Maybe there is something small being missed on
> the operation of sockets under windows?
> Original issue reported by *dguisinger*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)