You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Jason R. Coombs" <ja...@jaraco.com> on 2009/12/01 16:22:25 UTC
FW: SlikSVN 1.6.6 64-bit stalls on some operations
Greetings.
I've run into an issue with the latest release of SlikSVN
(1.6.6). I'm copying the problem description from an earlier mail to the
SlikSVN team, as the SlikSVN team has suggested I contact this list for
suggestions.
I've been using SlikSVN for all of my 64-bit Windows
systems. Beginning with 1.6.6, I found that the svn client frequently
stalls, for 120 seconds or more, on certain operations. It seems to stall in
particular at the following places:
1) At the beginning of a checkout operation, before copying any
files.
2) At the end of an import or checkin operation, after the server
has completed the transaction, but before the client reports the new
revision number.
3) At the end of an list operation, before returning control to
the parent process.
4) At the end of some update operations, before returning control
to the parent process.
While the client is stalling, I can check the network connections and see
that a TCP connection is open to the server, so the problem appears to be
related to some I/O blocking.
I've only observed this problem when working against my server, though I
spend only a small amount of time working with other servers. I haven't been
able to replicate the issue with Google or Sourceforge HTTPS servers. My
server is running SVN 1.6.6 on Apache 2.2.14 behind IIS via ISAPI Rewrite.
I do not experience the issue with the Tigris.org 1.6.6 svn client nor with
TortoiseSVN 1.6.6 client. I always experience the problem with the 32-bit
and 64-bit SlikSVN clients.
The problem can be easily replicated by requesting a list operation on
https://svn.jaraco.com/jaraco/python with the SlikSVN 1.6.6 client.
Obviously, the problem seems to be related to my server configuration as
well, but because the problem emerged with the latest release of the client,
and since the server works well with other clients, it makes the most sense
to determine what changed with the client.
The SlikSVN team has suggested I write this list to see if you have any
suggestions as to what might be causing the stalls. I suspect the problem
has something to do with the way that the I/O is handled. The problem
emerged with 1.6.6 and goes away if I roll back to SlikSVN 1.6.5.
Was there any change in the Subversion 1.6.5-1.6.6 changeset that might
affect the I/O behavior as described?
Do you have any other suggestions for troubleshooting this
issue?
Regards,
Jason
From: Jason R. Coombs
Sent: Tuesday, 24 November, 2009 10:39
To: Bert Huijben
Cc: 'Thijs Leydens (Slik BV)'
Subject: RE: SlikSVN 1.6.6 64-bit stalls on some operations
Hi Bert.
Thanks for the clarification. I'm used to build systems that
take the latest revision of the tree and not the revision of the repository
when tagging projects, and since the revision was from the trunk, I wanted
to be sure that wasn't the issue.
This means the issue I'm having is not related to the SVN
sources, but something specific to the SlikSVN build process (and also
specific to my server, it seems).
Did anything change with the SlikSVN build process between
1.6.5 and 1.6.6? Do you have instructions on how I could replicate the
SlikSVN build process locally so I can track down the issue?
Regards,
Jason
From: Bert Huijben [mailto:bert@qqmail.nl]
Sent: Tuesday, 24 November, 2009 04:57
To: Jason R. Coombs
Cc: 'Thijs Leydens (Slik BV)'
Subject: RE: SlikSVN 1.6.6 64-bit stalls on some operations
Hi Jason,
SlikSVN is not build against Subversion trunk. It is build against the
specific version tag (In this case
http://svn.collab.net/repos/svn/tags/1.6.6) at a specific revision. As the
SharpSvn binaries were build more than a week after the release of 1.6.6,
the revision at which the tag was retrieved is later than the one used to
generate the tarball.
(Actually the tarball was created against ^/branches/1.6.x). But all of this
only documents the exact procedure as there were no changes in between.
Once a release is tagged in the Subversion release, the tag should never
change..
If SlikSVN would be built from the subversion trunk sources you would have
dozens of other issues (probably many more). The Subversion trunk
development state doesn't have a guaranteed stable working copy format at
this time, so I would not recommend using it for developing anything outside
subversion itself.
And it would certainly make it impossible to share a working copy with any
other subversion client as the format currently changes every few weeks
until it reaches the final WC-NG state we like for Subversion 1.7.
Bert
From: Thijs Leydens (Slik BV) [mailto:thijs@slik.eu]
Sent: dinsdag 24 november 2009 9:22
To: bert@vmoo.com
Subject: FW: SlikSVN 1.6.6 64-bit stalls on some operations
From: Jason R. Coombs [mailto:jaraco@jaraco.com]
Sent: maandag 23 november 2009 19:07
To: support@sliksvn.com
Subject: RE: SlikSVN 1.6.6 64-bit stalls on some operations
Dear Thijs,
Let me first apologize for not taking your suggestion more seriously. My
initial instinct was that because I can only reproduce the problem with
SlikSVN that it must be a Slik SVN issue. but after some additional
information, I see how it could be a core subversion issue.
I've created a hybrid SlikSVN with the 1.6.6 binaries replaced with the
OpenSSL binaries from 1.6.5 and this had no effect, so the problem is
probably not due to the OpenSSL libraries.
I then noticed that SlikSVN is built against SVN r40358 while the Tigris.org
binaries are built against r40053. I now suspect that perhaps the issue
could reside between those revisions.
Can you confirm that the SlikSVN releases were built against a trunk
checkout of the SVN code? Was that done on purpose?
I sincerely appreciate you taking the time to help me resolve these issues.
If you can answer those straightforward questions, it will help me
significantly in tracking down the issue.
Best Regards,
Jason
From: Jason R. Coombs
Sent: Monday, 23 November, 2009 11:57
To: support@sliksvn.com
Subject: RE: SlikSVN 1.6.6 64-bit stalls on some operations
Dear Thijs,
Thanks for your prompt reply.
I'm concerned, however, that since I can't reproduce the
problem with the Tigris.org subversion client that there's nothing they can
investigate. Indeed, if I were them, based on my results, the first thing I
would recommend is to contact SlikSVN.
That is, I can run svn.exe from the svn-1.6.6-win32.zip
binary distribution for Windows and it doesn't stall, but if I run the same
command from the SlikSVN 1.6.6 distribution, it does stall.
I decided to run another test. I went to my server and
performed a list operation using SlikSVN directly to the Apache server not
through the SSL and reverse proxy. This test did not exhibit the stall,
which leads me to conclude that the issue lies between the SlikSVN 1.6.6
client and something in the SSL or HTTP handling on the client side.
Now I understand that the SlikSVN client works on other
SSL-enabled sites, so it's not strictly an SSL issue. However, it seems
likely to me that the compilation of the OpenSSL library with SlikSVN is one
of the likely differences between the Tigris.org binaries and SlikSVN
binaries.
I can continue to investigate. In the meantime, can you
confirm the OpenSSL versions used with SlikSVN 1.6.5 and 1.6.6?
Regards,
Jason
From: Thijs Leydens (Slik Subversion) [mailto:thijs@sliksvn.com]
Sent: Monday, 23 November, 2009 11:05
To: Jason R. Coombs
Cc: support@sliksvn.com
Subject: RE: SlikSVN 1.6.6 64-bit stalls on some operations
Hi Jason,
Sorry for not coming back to you; our SlikSVN client manager has been ill
for some time now.
I've been told that it is very unlikely that your issues are caused by our
binaries - it seems more like a Subversion issue than a SlikSVN issue. It's
probably best to forward your questions to users@subversion.tigris.org.
Best regards,
--
Thijs Leydens
Slik Developer Tools BV | A Slik company
Support: support@sliksvn.com | Tel +31 10 2827804 | Fax +31 10 2827805
Mauritsweg 49 | NL-3012 JW Rotterdam | The Netherlands | KvK 24441791
From: Jason R. Coombs [mailto:jaraco@jaraco.com]
Sent: maandag 23 november 2009 11:56
To: support@sliksvn.com
Subject: SlikSVN 1.6.6 64-bit stalls on some operations
Greetings,
I sent a message about this issue via the web support form a
couple of weeks ago. I didn't hear anything, so I'm resending in case the
first message was lost. I also have additional information over what I
reported before. I'm hoping this issue can be resolved for the next release.
I've been using SlikSVN for all of my 64-bit Windows
systems. Beginning with 1.6.6, I found that the svn client frequently
stalls, for 120 seconds or more, on certain operations. It seems to stall in
particular at the following places:
1) At the beginning of a checkout operation, before copying any files.
2) At the end of an import or checkin operation, after the server has
completed the transaction, but before the client reports the new revision
number.
3) At the end of an list operation, before returning control to the
parent process.
I think I've seen it stall on an update operation, but many updates complete
without the stall, so I may be mistaken.
While the client is stalling, I can check the network connections and see
that a TCP connection is open to the server, so the problem appears to be
related to some I/O blocking.
I've seen this problem on five separate installations of SlikSvn 1.6.6 (32-
and 64-bit) on Windows Vista, Windows 7, and Windows Server 2008. I've only
observed the problem when communicating with my server, which is SVN 1.6.6
behind Apache 2.2.14 behind IIS and ISAPI Rewrite. I had the same problem
with the 1.6.5 server, so I upgraded it to 1.6.6 to make sure that wasn't a
factor. I haven't observed this problem with any other server, though I use
my server most frequently.
I do not experience the stalls when using the Tigris.org 32-bit svn 1.6.6
client nor when using TortoiseSVN 1.6.6 (either 32- or 64-bit), so the
problem seems to be unique to my server and SlikSVN 1.6.6. I'd like to
continue to use SlikSVN's client, but these stalls are quite annoying.
I suspect you will be able to replicate the problem by performing a list on
https://svn.jaraco.com/jaraco/python/ .
It's quite possible the problem is related to my server, but since the
problem emerged between SlikSVN 1.6.5 and 1.6.6 and because the server works
reliably with other clients, I'm hoping a solution can be found with
SlikSVN. I'm happy to run test or debug code and help track down the issue.
I've never compiled an SVN client before, but I have Visual Studio 2008 and
I'm comfortable working through a procedure to set up the dependencies if
it's documented well enough. I didn't see SlikSVN source code on the web
site, though, so I understand if you're keeping that proprietary.
Please let me know if I can provide an additional information.
Regards,
Jason R. Coombs
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2425921
Please start new threads on the <us...@subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <us...@subversion.apache.org>.
RE: SlikSVN 1.6.6 64-bit stalls on some operations
Posted by "Jason R. Coombs" <ja...@jaraco.com>.
> From: Bert Huijben [mailto:bert@qqmail.nl]
>
> > -----Original Message-----
> > From: Jason R. Coombs [mailto:jaraco@jaraco.com]
> > Sent: woensdag 2 december 2009 13:15
> > To: Johan Corveleyn; users@subversion.tigris.org
> > Subject: RE: SlikSVN 1.6.6 64-bit stalls on some operations
> >
> > > From: Johan Corveleyn [mailto:johan.corveleyn@uz.kuleuven.ac.be]
> > > > Van: Jason R. Coombs [mailto:jaraco@jaraco.com]
> > > >
> > > > Greetings.
> > > >
> > > > I've run into an issue with the latest release of
> > > SlikSVN
> > > > (1.6.6). I'm copying the problem description from an earlier mail
> > to
> > > the
> > > > SlikSVN team, as the SlikSVN team has suggested I contact this
> list
> > > for
> > > > suggestions.
> > > >
> > > > I've been using SlikSVN for all of my 64-bit
> > Windows
> > > systems.
> > > > Beginning with 1.6.6, I found that the svn client frequently
> > stalls,
> > > for 120
> > > > seconds or more, on certain operations. It seems to stall in
> > > particular at
> > > > the following places:
> > > >
> > > > 1) At the beginning of a checkout operation, before
> > > copying any
> > > > files.
> > > > 2) At the end of an import or checkin operation, after
> > the
> > > server
> > > > has completed the transaction, but before the client reports the
> > new
> > > revision
> > > > number.
> > > > 3) At the end of an list operation, before returning
> > > control to
> > > > the parent process.
> > > > 4) At the end of some update operations, before
> > returning
> > > control
> > > > to the parent process.
> > > >
> > > > While the client is stalling, I can check the network
> > > connections and
> > > > see that a TCP connection is open to the server, so the problem
> > > appears to be
> > > > related to some I/O blocking.
> > > >
> > > > I've only observed this problem when working against my
> > > server, though
> > > > I spend only a small amount of time working with other servers. I
> > > haven't
> > > > been able to replicate the issue with Google or Sourceforge HTTPS
> > > servers. My
> > > > server is running SVN 1.6.6 on Apache 2.2.14 behind IIS via ISAPI
> > > Rewrite.
> > > >
> > > > I do not experience the issue with the Tigris.org 1.6.6
> svn
> > > client nor
> > > > with TortoiseSVN 1.6.6 client. I always experience the problem
> with
> > > the 32-
> > > > bit and 64-bit SlikSVN clients.
> > > >
> > > > The problem can be easily replicated by requesting a list
> > > operation on
> > > > https://svn.jaraco.com/jaraco/python with the SlikSVN 1.6.6
> client.
> > > > Obviously, the problem seems to be related to my server
> > configuration
> > > as
> > > > well, but because the problem emerged with the latest release of
> > the
> > > client,
> > > > and since the server works well with other clients, it makes the
> > most
> > > sense
> > > > to determine what changed with the client.
> > > >
> > > > The SlikSVN team has suggested I write this list to see if
> > you
> > > have
> > > > any suggestions as to what might be causing the stalls. I suspect
> > the
> > > problem
> > > > has something to do with the way that the I/O is handled. The
> > problem
> > > emerged
> > > > with 1.6.6 and goes away if I roll back to SlikSVN 1.6.5.
> > > >
> > > > Was there any change in the Subversion 1.6.5-1.6.6
> changeset
> > > that
> > > > might affect the I/O behavior as described?
> > > >
> > > > Do you have any other suggestions for
> > troubleshooting
> > > this
> > > > issue?
> > >
> > > That is ... weird. Especially the fact that you only get the issue
> > with
> > > SlikSVN 1.6.6 (and not with other windows binaries nor with other
> > > versions of SlikSVN), and only in combination with your server (and
> > not
> > > with other (public) https servers).
> > >
> > > I don't have time to reproduce or investigate myself, but just some
> > > ideas:
> > >
> > > - Is there anything that you can think of that makes a difference
> > > between your server and google or sourceforge servers? I'm thinking
> > of
> > > things like http compression (use of DEFLATE filters in your apache
> > > config, and of http-compression in your client-side configuration),
> > and
> > > proxy servers (any of those connections going through a proxy, as
> > > opposed to the others?). Also, maybe you're accessing your own
> server
> > > through another (internal) network route than google or
> sourceforge?
> > > Maybe there's a difference in proxies, firewalls, ...?
> >
> > The SSL is handled by IIS, and the results are "reverse" proxied to
> > Apache
> > via ISAPI-Rewrite. This is very likely another factor driving the
> > issue. I
> > have not yet had the luxury to disable SSL and determine if the
> problem
> > is
> > related to SSL. I don't have the luxury of configuring Apache as the
> > front-end server for two reasons: First, I need to maintain the
> server
> > on
> > one IP address and have other IIS applications that must also be
> served
> > from
> > that address. Second, it's much easier to maintain one front-end SSL
> > server
> > (IIS) versus having to keep two servers maintained.
> >
> > The problem does not appear to be related to firewalls or other local
> > phenomena. The problem occurs across the Internet the same as
> locally.
> > It
> > occurs whether firewalls are present or not. No proxies, other than
> the
> > one
> > used to reverse-proxy the IIS front-end requests to the back-end
> Apache
> > server are used.
> >
> > > - Any specific configuration in your client-side "servers"
> > > configuration file?
> >
> > No. This happens with a clean install.
> >
> > > - Can you also reproduce this on a 32-bit Windows system?
> >
> > Yes. But again, only with SlikSVN.
> >
> > > - Are you using neon or serf for any of those connections (default
> in
> > > 1.6.x is still neon, I believe, but you can configure serf in your
> > > "servers" file, or by command line option)?
> >
> > It's using the default.
> >
> > > - Since it only happens with SlikSVN 1.6.6, and not with the
> > tigris.org
> > > 1.6.6 svn client, it must have something to do with differences in
> > how
> > > they were built (both clients do pick up the same client-side
> config,
> > > don't they?). Dependencies on other libraries come to mind: maybe
> > they
> > > were built against a different version of neon, serf, zlib, apr-
> util,
> > > ... ? I don't know how you can check that, maybe you'll have to ask
> > the
> > > people who made those binaries ...
> >
> > Yes, both clients use the same config.
> >
> > > - There might also be other slight differences in the way SlikSVN
> is
> > > built as opposed to the tigris.org client. Maybe they use another
> > > compiler version, another Microsoft SDK, other compiler options,
> ...
> > > but that's very difficult to investigate (there can be lots of such
> > > small differences).
> >
> > I'd even be happy if I rebuilt it and the problem went away.
> > Unfortunately,
> > I don't think SlikSVN is willing to share their build process with
> me.
> > I may
> > end up having to make my own build for 64-bit Windows clients.
>
> The entire build process of SlikSVN distribution is part of the
> SharpSvn sourcecode.
>
> The latest version (which is used for SlikSVN 1.6.6) is in
> http://sharpsvn.open.collab.net/svn/sharpsvn/trunk/ (username guest; no
> password. Or a valid open collabnet account)
>
> After installing the prerequisites (Visual Studio 2005/2008, Python,
> Perl, NAnt, Subversion client) you can run 'nant build' in
> trunk/imports/svn-dist to replicate the SlikSvn build. (MSI generation
> scripts using Wix are in a subdir).
>
> To replicate the exact build you need VS 2008 with all available
> updates (SP1 + Several security patches).
>
> Bert
Thanks Bert for the suggestion on how to build. I ran into an error when
trying to build:
...
[Svn] A
C:\Users\jaraco\projects\public\sharpsvn\imports\svn-dist\build
\sqlite\README
[Svn] Checked out revision 1386.
prepare-bdb:
[VCBuild] Unable to convert project.
[VCBuild] Please make sure this is a valid Visual C++ 4.0 or later project.
BUILD FAILED - 0 non-fatal error(s), 2 warning(s)
C:\Users\jaraco\projects\public\sharpsvn\imports\scripts\bdb.build(24,12):
External Program Failed: vcbuild.exe (return code was -1)
Total time: 571.8 seconds.
I have installed all of the prerequisites except Visual Studio 2008. I instead
have Visual C++ Express 2008 and Visual C# Express 2008. I am running from a
"Visual Studio 2008 Command Prompt" in order to have the development
environment variables loaded, and I can run VCBuild.exe from that prompt and
get the VCBuild usage.
Can you confirm that Visual Studio Express Edition should work or is known not
to work? Do you have any other suggestions on how to work around this build
issue?
Regards,
Jason
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2428024
Please start new threads on the <us...@subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <us...@subversion.apache.org>.
RE: SlikSVN 1.6.6 64-bit stalls on some operations
Posted by Bert Huijben <rh...@sharpsvn.net>.
> -----Original Message-----
> From: Jason R. Coombs [mailto:jaraco@jaraco.com]
> Sent: woensdag 2 december 2009 13:15
> To: Johan Corveleyn; users@subversion.tigris.org
> Subject: RE: SlikSVN 1.6.6 64-bit stalls on some operations
>
> > From: Johan Corveleyn [mailto:johan.corveleyn@uz.kuleuven.ac.be]
> > > Van: Jason R. Coombs [mailto:jaraco@jaraco.com]
> > >
> > > Greetings.
> > >
> > > I've run into an issue with the latest release of
> > SlikSVN
> > > (1.6.6). I'm copying the problem description from an earlier mail
> to
> > the
> > > SlikSVN team, as the SlikSVN team has suggested I contact this list
> > for
> > > suggestions.
> > >
> > > I've been using SlikSVN for all of my 64-bit
> Windows
> > systems.
> > > Beginning with 1.6.6, I found that the svn client frequently
> stalls,
> > for 120
> > > seconds or more, on certain operations. It seems to stall in
> > particular at
> > > the following places:
> > >
> > > 1) At the beginning of a checkout operation, before
> > copying any
> > > files.
> > > 2) At the end of an import or checkin operation, after
> the
> > server
> > > has completed the transaction, but before the client reports the
> new
> > revision
> > > number.
> > > 3) At the end of an list operation, before returning
> > control to
> > > the parent process.
> > > 4) At the end of some update operations, before
> returning
> > control
> > > to the parent process.
> > >
> > > While the client is stalling, I can check the network
> > connections and
> > > see that a TCP connection is open to the server, so the problem
> > appears to be
> > > related to some I/O blocking.
> > >
> > > I've only observed this problem when working against my
> > server, though
> > > I spend only a small amount of time working with other servers. I
> > haven't
> > > been able to replicate the issue with Google or Sourceforge HTTPS
> > servers. My
> > > server is running SVN 1.6.6 on Apache 2.2.14 behind IIS via ISAPI
> > Rewrite.
> > >
> > > I do not experience the issue with the Tigris.org 1.6.6 svn
> > client nor
> > > with TortoiseSVN 1.6.6 client. I always experience the problem with
> > the 32-
> > > bit and 64-bit SlikSVN clients.
> > >
> > > The problem can be easily replicated by requesting a list
> > operation on
> > > https://svn.jaraco.com/jaraco/python with the SlikSVN 1.6.6 client.
> > > Obviously, the problem seems to be related to my server
> configuration
> > as
> > > well, but because the problem emerged with the latest release of
> the
> > client,
> > > and since the server works well with other clients, it makes the
> most
> > sense
> > > to determine what changed with the client.
> > >
> > > The SlikSVN team has suggested I write this list to see if
> you
> > have
> > > any suggestions as to what might be causing the stalls. I suspect
> the
> > problem
> > > has something to do with the way that the I/O is handled. The
> problem
> > emerged
> > > with 1.6.6 and goes away if I roll back to SlikSVN 1.6.5.
> > >
> > > Was there any change in the Subversion 1.6.5-1.6.6 changeset
> > that
> > > might affect the I/O behavior as described?
> > >
> > > Do you have any other suggestions for
> troubleshooting
> > this
> > > issue?
> >
> > That is ... weird. Especially the fact that you only get the issue
> with
> > SlikSVN 1.6.6 (and not with other windows binaries nor with other
> > versions of SlikSVN), and only in combination with your server (and
> not
> > with other (public) https servers).
> >
> > I don't have time to reproduce or investigate myself, but just some
> > ideas:
> >
> > - Is there anything that you can think of that makes a difference
> > between your server and google or sourceforge servers? I'm thinking
> of
> > things like http compression (use of DEFLATE filters in your apache
> > config, and of http-compression in your client-side configuration),
> and
> > proxy servers (any of those connections going through a proxy, as
> > opposed to the others?). Also, maybe you're accessing your own server
> > through another (internal) network route than google or sourceforge?
> > Maybe there's a difference in proxies, firewalls, ...?
>
> The SSL is handled by IIS, and the results are "reverse" proxied to
> Apache
> via ISAPI-Rewrite. This is very likely another factor driving the
> issue. I
> have not yet had the luxury to disable SSL and determine if the problem
> is
> related to SSL. I don't have the luxury of configuring Apache as the
> front-end server for two reasons: First, I need to maintain the server
> on
> one IP address and have other IIS applications that must also be served
> from
> that address. Second, it's much easier to maintain one front-end SSL
> server
> (IIS) versus having to keep two servers maintained.
>
> The problem does not appear to be related to firewalls or other local
> phenomena. The problem occurs across the Internet the same as locally.
> It
> occurs whether firewalls are present or not. No proxies, other than the
> one
> used to reverse-proxy the IIS front-end requests to the back-end Apache
> server are used.
>
> > - Any specific configuration in your client-side "servers"
> > configuration file?
>
> No. This happens with a clean install.
>
> > - Can you also reproduce this on a 32-bit Windows system?
>
> Yes. But again, only with SlikSVN.
>
> > - Are you using neon or serf for any of those connections (default in
> > 1.6.x is still neon, I believe, but you can configure serf in your
> > "servers" file, or by command line option)?
>
> It's using the default.
>
> > - Since it only happens with SlikSVN 1.6.6, and not with the
> tigris.org
> > 1.6.6 svn client, it must have something to do with differences in
> how
> > they were built (both clients do pick up the same client-side config,
> > don't they?). Dependencies on other libraries come to mind: maybe
> they
> > were built against a different version of neon, serf, zlib, apr-util,
> > ... ? I don't know how you can check that, maybe you'll have to ask
> the
> > people who made those binaries ...
>
> Yes, both clients use the same config.
>
> > - There might also be other slight differences in the way SlikSVN is
> > built as opposed to the tigris.org client. Maybe they use another
> > compiler version, another Microsoft SDK, other compiler options, ...
> > but that's very difficult to investigate (there can be lots of such
> > small differences).
>
> I'd even be happy if I rebuilt it and the problem went away.
> Unfortunately,
> I don't think SlikSVN is willing to share their build process with me.
> I may
> end up having to make my own build for 64-bit Windows clients.
The entire build process of SlikSVN distribution is part of the SharpSvn sourcecode.
The latest version (which is used for SlikSVN 1.6.6) is in
http://sharpsvn.open.collab.net/svn/sharpsvn/trunk/ (username guest; no password. Or a valid open collabnet account)
After installing the prerequisites (Visual Studio 2005/2008, Python, Perl, NAnt, Subversion client) you can run 'nant build' in trunk/imports/svn-dist to replicate the SlikSvn build. (MSI generation scripts using Wix are in a subdir).
To replicate the exact build you need VS 2008 with all available updates (SP1 + Several security patches).
Bert
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2426325
Please start new threads on the <us...@subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <us...@subversion.apache.org>.
RE: SlikSVN 1.6.6 64-bit stalls on some operations
Posted by "Jason R. Coombs" <ja...@jaraco.com>.
> From: Ryan Schmidt [mailto:subversion-2009d@ryandesign.com]
>
> On Dec 2, 2009, at 06:14, Jason R. Coombs wrote:
>
> Have you already tried accessing your Apache server directly, bypassing
> the IIS proxy? The IIS part is almost certainly a unique part of your
> setup, and could well be the source of your problems.
>
I just ran a few more tests and confirmed that the problem does not occur
when I connect to the Apache server directly nor when I enable HTTP access
and connect to the IIS site but without SSL.
So the problem is appears to be related to the SSL handshaking between the
SlikSVN 1.6.6 build and IIS 7.
And as I mentioned before, I suspected the problem might be related to the
server as well, but since I've had this server in production for years, and
since the problem only recently emerged with the upgrade from SlikSVN 1.6.5
to 1.6.6, and since the problem does not occur with other svn 1.6.6 clients,
it is only logical to try to tackle the problem from the direction of the
primary variable - the client.
I realize that I could host my repositories elsewhere, but then I would lose
integrated authentication and free storage. I realize I could host the site
directly on Apache, but then I require additional IP infrastructure and more
complicated maintenance procedures. I could just switch to using a 32-bit
client, but then I must maintain duplicate copies of the client settings on
each of my machines (one for the 32-bit client and one for the 64-bit
clients).
Of course, what I'd prefer to do is track down what's causing the problem
and correct it.
I think with Bert's last e-mail, I should be able to replicate the build -
and with that track down the cause.
Let me know if you have any other insight into what might cause the stalls
only against an IIS 7 HTTPS session.
Regards,
Jason
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2426421
Please start new threads on the <us...@subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <us...@subversion.apache.org>.
Re: SlikSVN 1.6.6 64-bit stalls on some operations
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Dec 2, 2009, at 06:14, Jason R. Coombs wrote:
> The SSL is handled by IIS, and the results are "reverse" proxied to Apache
> via ISAPI-Rewrite. This is very likely another factor driving the issue. I
> have not yet had the luxury to disable SSL and determine if the problem is
> related to SSL. I don't have the luxury of configuring Apache as the
> front-end server for two reasons: First, I need to maintain the server on
> one IP address and have other IIS applications that must also be served from
> that address. Second, it's much easier to maintain one front-end SSL server
> (IIS) versus having to keep two servers maintained.
Have you already tried accessing your Apache server directly, bypassing the IIS proxy? The IIS part is almost certainly a unique part of your setup, and could well be the source of your problems.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2426410
Please start new threads on the <us...@subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <us...@subversion.apache.org>.
RE: SlikSVN 1.6.6 64-bit stalls on some operations
Posted by "Jason R. Coombs" <ja...@jaraco.com>.
> From: Johan Corveleyn [mailto:johan.corveleyn@uz.kuleuven.ac.be]
> > Van: Jason R. Coombs [mailto:jaraco@jaraco.com]
> >
> > Greetings.
> >
> > I've run into an issue with the latest release of
> SlikSVN
> > (1.6.6). I'm copying the problem description from an earlier mail to
> the
> > SlikSVN team, as the SlikSVN team has suggested I contact this list
> for
> > suggestions.
> >
> > I've been using SlikSVN for all of my 64-bit Windows
> systems.
> > Beginning with 1.6.6, I found that the svn client frequently stalls,
> for 120
> > seconds or more, on certain operations. It seems to stall in
> particular at
> > the following places:
> >
> > 1) At the beginning of a checkout operation, before
> copying any
> > files.
> > 2) At the end of an import or checkin operation, after the
> server
> > has completed the transaction, but before the client reports the new
> revision
> > number.
> > 3) At the end of an list operation, before returning
> control to
> > the parent process.
> > 4) At the end of some update operations, before returning
> control
> > to the parent process.
> >
> > While the client is stalling, I can check the network
> connections and
> > see that a TCP connection is open to the server, so the problem
> appears to be
> > related to some I/O blocking.
> >
> > I've only observed this problem when working against my
> server, though
> > I spend only a small amount of time working with other servers. I
> haven't
> > been able to replicate the issue with Google or Sourceforge HTTPS
> servers. My
> > server is running SVN 1.6.6 on Apache 2.2.14 behind IIS via ISAPI
> Rewrite.
> >
> > I do not experience the issue with the Tigris.org 1.6.6 svn
> client nor
> > with TortoiseSVN 1.6.6 client. I always experience the problem with
> the 32-
> > bit and 64-bit SlikSVN clients.
> >
> > The problem can be easily replicated by requesting a list
> operation on
> > https://svn.jaraco.com/jaraco/python with the SlikSVN 1.6.6 client.
> > Obviously, the problem seems to be related to my server configuration
> as
> > well, but because the problem emerged with the latest release of the
> client,
> > and since the server works well with other clients, it makes the most
> sense
> > to determine what changed with the client.
> >
> > The SlikSVN team has suggested I write this list to see if you
> have
> > any suggestions as to what might be causing the stalls. I suspect the
> problem
> > has something to do with the way that the I/O is handled. The problem
> emerged
> > with 1.6.6 and goes away if I roll back to SlikSVN 1.6.5.
> >
> > Was there any change in the Subversion 1.6.5-1.6.6 changeset
> that
> > might affect the I/O behavior as described?
> >
> > Do you have any other suggestions for troubleshooting
> this
> > issue?
>
> That is ... weird. Especially the fact that you only get the issue with
> SlikSVN 1.6.6 (and not with other windows binaries nor with other
> versions of SlikSVN), and only in combination with your server (and not
> with other (public) https servers).
>
> I don't have time to reproduce or investigate myself, but just some
> ideas:
>
> - Is there anything that you can think of that makes a difference
> between your server and google or sourceforge servers? I'm thinking of
> things like http compression (use of DEFLATE filters in your apache
> config, and of http-compression in your client-side configuration), and
> proxy servers (any of those connections going through a proxy, as
> opposed to the others?). Also, maybe you're accessing your own server
> through another (internal) network route than google or sourceforge?
> Maybe there's a difference in proxies, firewalls, ...?
The SSL is handled by IIS, and the results are "reverse" proxied to Apache
via ISAPI-Rewrite. This is very likely another factor driving the issue. I
have not yet had the luxury to disable SSL and determine if the problem is
related to SSL. I don't have the luxury of configuring Apache as the
front-end server for two reasons: First, I need to maintain the server on
one IP address and have other IIS applications that must also be served from
that address. Second, it's much easier to maintain one front-end SSL server
(IIS) versus having to keep two servers maintained.
The problem does not appear to be related to firewalls or other local
phenomena. The problem occurs across the Internet the same as locally. It
occurs whether firewalls are present or not. No proxies, other than the one
used to reverse-proxy the IIS front-end requests to the back-end Apache
server are used.
> - Any specific configuration in your client-side "servers"
> configuration file?
No. This happens with a clean install.
> - Can you also reproduce this on a 32-bit Windows system?
Yes. But again, only with SlikSVN.
> - Are you using neon or serf for any of those connections (default in
> 1.6.x is still neon, I believe, but you can configure serf in your
> "servers" file, or by command line option)?
It's using the default.
> - Since it only happens with SlikSVN 1.6.6, and not with the tigris.org
> 1.6.6 svn client, it must have something to do with differences in how
> they were built (both clients do pick up the same client-side config,
> don't they?). Dependencies on other libraries come to mind: maybe they
> were built against a different version of neon, serf, zlib, apr-util,
> ... ? I don't know how you can check that, maybe you'll have to ask the
> people who made those binaries ...
Yes, both clients use the same config.
> - There might also be other slight differences in the way SlikSVN is
> built as opposed to the tigris.org client. Maybe they use another
> compiler version, another Microsoft SDK, other compiler options, ...
> but that's very difficult to investigate (there can be lots of such
> small differences).
I'd even be happy if I rebuilt it and the problem went away. Unfortunately,
I don't think SlikSVN is willing to share their build process with me. I may
end up having to make my own build for 64-bit Windows clients.
> If all else fails, I think you'll have to try and troubleshoot this
> with some low-level Windows tools, things like sysinternals
> (http://technet.microsoft.com/en-us/sysinternals/default.aspx), and the
> like ... but then you may be in for a long ride.
Thanks for the suggestions. I think I'll disable SSL on the server (or
enable plaintext HTTP rather) and use wireshark to monitor the traffic.
Perhaps that will elucidate something. I'm familiar with the SysInternals
tools, so I'll give those a go also.
Thanks for Subversion and Regards,
Jason
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2426312
Please start new threads on the <us...@subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <us...@subversion.apache.org>.
RE: SlikSVN 1.6.6 64-bit stalls on some operations
Posted by Johan Corveleyn <jo...@uz.kuleuven.ac.be>.
> Van: Jason R. Coombs [mailto:jaraco@jaraco.com]
>
> Greetings.
>
> I've run into an issue with the latest release of SlikSVN
> (1.6.6). I'm copying the problem description from an earlier mail to the
> SlikSVN team, as the SlikSVN team has suggested I contact this list for
> suggestions.
>
> I've been using SlikSVN for all of my 64-bit Windows systems.
> Beginning with 1.6.6, I found that the svn client frequently stalls, for 120
> seconds or more, on certain operations. It seems to stall in particular at
> the following places:
>
> 1) At the beginning of a checkout operation, before copying any
> files.
> 2) At the end of an import or checkin operation, after the server
> has completed the transaction, but before the client reports the new revision
> number.
> 3) At the end of an list operation, before returning control to
> the parent process.
> 4) At the end of some update operations, before returning control
> to the parent process.
>
> While the client is stalling, I can check the network connections and
> see that a TCP connection is open to the server, so the problem appears to be
> related to some I/O blocking.
>
> I've only observed this problem when working against my server, though
> I spend only a small amount of time working with other servers. I haven't
> been able to replicate the issue with Google or Sourceforge HTTPS servers. My
> server is running SVN 1.6.6 on Apache 2.2.14 behind IIS via ISAPI Rewrite.
>
> I do not experience the issue with the Tigris.org 1.6.6 svn client nor
> with TortoiseSVN 1.6.6 client. I always experience the problem with the 32-
> bit and 64-bit SlikSVN clients.
>
> The problem can be easily replicated by requesting a list operation on
> https://svn.jaraco.com/jaraco/python with the SlikSVN 1.6.6 client.
> Obviously, the problem seems to be related to my server configuration as
> well, but because the problem emerged with the latest release of the client,
> and since the server works well with other clients, it makes the most sense
> to determine what changed with the client.
>
> The SlikSVN team has suggested I write this list to see if you have
> any suggestions as to what might be causing the stalls. I suspect the problem
> has something to do with the way that the I/O is handled. The problem emerged
> with 1.6.6 and goes away if I roll back to SlikSVN 1.6.5.
>
> Was there any change in the Subversion 1.6.5-1.6.6 changeset that
> might affect the I/O behavior as described?
>
> Do you have any other suggestions for troubleshooting this
> issue?
That is ... weird. Especially the fact that you only get the issue with SlikSVN 1.6.6 (and not with other windows binaries nor with other versions of SlikSVN), and only in combination with your server (and not with other (public) https servers).
I don't have time to reproduce or investigate myself, but just some ideas:
- Is there anything that you can think of that makes a difference between your server and google or sourceforge servers? I'm thinking of things like http compression (use of DEFLATE filters in your apache config, and of http-compression in your client-side configuration), and proxy servers (any of those connections going through a proxy, as opposed to the others?). Also, maybe you're accessing your own server through another (internal) network route than google or sourceforge? Maybe there's a difference in proxies, firewalls, ...?
- Any specific configuration in your client-side "servers" configuration file?
- Can you also reproduce this on a 32-bit Windows system?
- Are you using neon or serf for any of those connections (default in 1.6.x is still neon, I believe, but you can configure serf in your "servers" file, or by command line option)?
- Since it only happens with SlikSVN 1.6.6, and not with the tigris.org 1.6.6 svn client, it must have something to do with differences in how they were built (both clients do pick up the same client-side config, don't they?). Dependencies on other libraries come to mind: maybe they were built against a different version of neon, serf, zlib, apr-util, ... ? I don't know how you can check that, maybe you'll have to ask the people who made those binaries ...
- There might also be other slight differences in the way SlikSVN is built as opposed to the tigris.org client. Maybe they use another compiler version, another Microsoft SDK, other compiler options, ... but that's very difficult to investigate (there can be lots of such small differences).
If all else fails, I think you'll have to try and troubleshoot this with some low-level Windows tools, things like sysinternals (http://technet.microsoft.com/en-us/sysinternals/default.aspx), and the like ... but then you may be in for a long ride.
HTH
Regards,
Johan
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2426272
Please start new threads on the <us...@subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <us...@subversion.apache.org>.
RE: FW: SlikSVN 1.6.6 64-bit stalls on some operations
Posted by "Jason R. Coombs" <ja...@jaraco.com>.
Thanks Bert!
And thanks http://twitter.com/thomykay !
> -----Original Message-----
> From: Bert Huijben [mailto:bert@qqmail.nl]
>
> It looks like I can reproduce this issue when using SvnBridge as
> installed by codeplex.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2432305
Please start new threads on the <us...@subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <us...@subversion.apache.org>.
Re: FW: SlikSVN 1.6.6 64-bit stalls on some operations
Posted by Bert Huijben <rh...@sharpsvn.net>.
On Tue, Dec 1, 2009 at 5:22 PM, Jason R. Coombs <ja...@jaraco.com> wrote:
> Greetings.
>
>
>
> I’ve run into an issue with the latest release of SlikSVN
> (1.6.6). I’m copying the problem description from an earlier mail to the
> SlikSVN team, as the SlikSVN team has suggested I contact this list for
> suggestions.
>
>
>
> I’ve been using SlikSVN for all of my 64-bit Windows
> systems. Beginning with 1.6.6, I found that the svn client frequently
> stalls, for 120 seconds or more, on certain operations. It seems to stall in
> particular at the following places:
It looks like I can reproduce this issue when using SvnBridge as
installed by codeplex.
E.g.
svn ls https://svnbridge.svn.codeplex.com/svn/ stalls after all the
output is done.
Debugging this issue further it seems related to a change in more
recent neon versions combined with several other ssl implementations
than apache.
Since r1726, neon tries to perform a bidirectional shutdown of SSL
connections (new in 0.29.0), which seems to stall the connection until
the connection times out for these implementations.
I plan to revert (reverse merge) this change in my neon build for the
next SlikSVN and SharpSvn+AnkhSVN release, to revert to the old
behavior.
Bert
PS. Thanks to http://twitter.com/thomykay for helping us find a
reproduction recipe.
>
>
>
> 1) At the beginning of a checkout operation, before copying any
> files.
>
> 2) At the end of an import or checkin operation, after the server
> has completed the transaction, but before the client reports the new
> revision number.
>
> 3) At the end of an list operation, before returning control to
> the parent process.
>
> 4) At the end of some update operations, before returning control
> to the parent process.
>
>
>
> While the client is stalling, I can check the network connections and see
> that a TCP connection is open to the server, so the problem appears to be
> related to some I/O blocking.
>
>
>
> I’ve only observed this problem when working against my server, though I
> spend only a small amount of time working with other servers. I haven’t been
> able to replicate the issue with Google or Sourceforge HTTPS servers. My
> server is running SVN 1.6.6 on Apache 2.2.14 behind IIS via ISAPI Rewrite.
>
>
>
> I do not experience the issue with the Tigris.org 1.6.6 svn client nor with
> TortoiseSVN 1.6.6 client. I always experience the problem with the 32-bit
> and 64-bit SlikSVN clients.
>
>
>
> The problem can be easily replicated by requesting a list operation on
> https://svn.jaraco.com/jaraco/python with the SlikSVN 1.6.6 client.
> Obviously, the problem seems to be related to my server configuration as
> well, but because the problem emerged with the latest release of the client,
> and since the server works well with other clients, it makes the most sense
> to determine what changed with the client.
>
>
>
> The SlikSVN team has suggested I write this list to see if you have any
> suggestions as to what might be causing the stalls. I suspect the problem
> has something to do with the way that the I/O is handled. The problem
> emerged with 1.6.6 and goes away if I roll back to SlikSVN 1.6.5.
>
>
>
> Was there any change in the Subversion 1.6.5-1.6.6 changeset that might
> affect the I/O behavior as described?
>
>
>
> Do you have any other suggestions for troubleshooting this
> issue?
>
>
>
> Regards,
>
> Jason
>
>
>
>
>
> From: Jason R. Coombs
> Sent: Tuesday, 24 November, 2009 10:39
> To: Bert Huijben
> Cc: 'Thijs Leydens (Slik BV)'
> Subject: RE: SlikSVN 1.6.6 64-bit stalls on some operations
>
>
>
> Hi Bert.
>
>
>
> Thanks for the clarification. I’m used to build systems that
> take the latest revision of the tree and not the revision of the repository
> when tagging projects, and since the revision was from the trunk, I wanted
> to be sure that wasn’t the issue.
>
>
>
> This means the issue I’m having is not related to the SVN
> sources, but something specific to the SlikSVN build process (and also
> specific to my server, it seems).
>
>
>
> Did anything change with the SlikSVN build process between
> 1.6.5 and 1.6.6? Do you have instructions on how I could replicate the
> SlikSVN build process locally so I can track down the issue?
>
>
>
> Regards,
>
> Jason
>
>
>
> From: Bert Huijben [mailto:bert@qqmail.nl]
> Sent: Tuesday, 24 November, 2009 04:57
> To: Jason R. Coombs
> Cc: 'Thijs Leydens (Slik BV)'
> Subject: RE: SlikSVN 1.6.6 64-bit stalls on some operations
>
>
>
> Hi Jason,
>
>
>
> SlikSVN is not build against Subversion trunk. It is build against the
> specific version tag (In this case
> http://svn.collab.net/repos/svn/tags/1.6.6) at a specific revision. As the
> SharpSvn binaries were build more than a week after the release of 1.6.6,
> the revision at which the tag was retrieved is later than the one used to
> generate the tarball.
>
> (Actually the tarball was created against ^/branches/1.6.x). But all of this
> only documents the exact procedure as there were no changes in between.
>
>
>
> Once a release is tagged in the Subversion release, the tag should never
> change..
>
>
>
>
>
> If SlikSVN would be built from the subversion trunk sources you would have
> dozens of other issues (probably many more). The Subversion trunk
> development state doesn’t have a guaranteed stable working copy format at
> this time, so I would not recommend using it for developing anything outside
> subversion itself.
>
>
>
> And it would certainly make it impossible to share a working copy with any
> other subversion client as the format currently changes every few weeks
> until it reaches the final WC-NG state we like for Subversion 1.7.
>
>
>
> Bert
>
>
>
>
>
> From: Thijs Leydens (Slik BV) [mailto:thijs@slik.eu]
> Sent: dinsdag 24 november 2009 9:22
> To: bert@vmoo.com
> Subject: FW: SlikSVN 1.6.6 64-bit stalls on some operations
>
>
>
>
>
>
>
> From: Jason R. Coombs [mailto:jaraco@jaraco.com]
> Sent: maandag 23 november 2009 19:07
> To: support@sliksvn.com
> Subject: RE: SlikSVN 1.6.6 64-bit stalls on some operations
>
>
>
> Dear Thijs,
>
>
>
> Let me first apologize for not taking your suggestion more seriously. My
> initial instinct was that because I can only reproduce the problem with
> SlikSVN that it must be a Slik SVN issue… but after some additional
> information, I see how it could be a core subversion issue.
>
>
>
> I’ve created a hybrid SlikSVN with the 1.6.6 binaries replaced with the
> OpenSSL binaries from 1.6.5 and this had no effect, so the problem is
> probably not due to the OpenSSL libraries.
>
>
>
> I then noticed that SlikSVN is built against SVN r40358 while the Tigris.org
> binaries are built against r40053. I now suspect that perhaps the issue
> could reside between those revisions.
>
>
>
> Can you confirm that the SlikSVN releases were built against a trunk
> checkout of the SVN code? Was that done on purpose?
>
>
>
> I sincerely appreciate you taking the time to help me resolve these issues.
> If you can answer those straightforward questions, it will help me
> significantly in tracking down the issue.
>
>
>
> Best Regards,
>
> Jason
>
>
>
> From: Jason R. Coombs
> Sent: Monday, 23 November, 2009 11:57
> To: support@sliksvn.com
> Subject: RE: SlikSVN 1.6.6 64-bit stalls on some operations
>
>
>
> Dear Thijs,
>
>
>
> Thanks for your prompt reply.
>
>
>
> I’m concerned, however, that since I can’t reproduce the
> problem with the Tigris.org subversion client that there’s nothing they can
> investigate. Indeed, if I were them, based on my results, the first thing I
> would recommend is to contact SlikSVN.
>
>
>
> That is, I can run svn.exe from the svn-1.6.6-win32.zip
> binary distribution for Windows and it doesn’t stall, but if I run the same
> command from the SlikSVN 1.6.6 distribution, it does stall.
>
>
>
> I decided to run another test. I went to my server and
> performed a list operation using SlikSVN directly to the Apache server not
> through the SSL and reverse proxy. This test did not exhibit the stall,
> which leads me to conclude that the issue lies between the SlikSVN 1.6.6
> client and something in the SSL or HTTP handling on the client side.
>
>
>
> Now I understand that the SlikSVN client works on other
> SSL-enabled sites, so it’s not strictly an SSL issue. However, it seems
> likely to me that the compilation of the OpenSSL library with SlikSVN is one
> of the likely differences between the Tigris.org binaries and SlikSVN
> binaries.
>
>
>
> I can continue to investigate. In the meantime, can you
> confirm the OpenSSL versions used with SlikSVN 1.6.5 and 1.6.6?
>
>
>
> Regards,
>
> Jason
>
>
>
> From: Thijs Leydens (Slik Subversion) [mailto:thijs@sliksvn.com]
> Sent: Monday, 23 November, 2009 11:05
> To: Jason R. Coombs
> Cc: support@sliksvn.com
> Subject: RE: SlikSVN 1.6.6 64-bit stalls on some operations
>
>
>
> Hi Jason,
>
>
>
> Sorry for not coming back to you; our SlikSVN client manager has been ill
> for some time now.
>
>
>
> I’ve been told that it is very unlikely that your issues are caused by our
> binaries – it seems more like a Subversion issue than a SlikSVN issue. It’s
> probably best to forward your questions to users@subversion.tigris.org.
>
>
>
> Best regards,
>
>
>
>
>
> --
>
> Thijs Leydens
>
> Slik Developer Tools BV | A Slik company
>
> Support: support@sliksvn.com | Tel +31 10 2827804 | Fax +31 10 2827805
>
> Mauritsweg 49 | NL-3012 JW Rotterdam | The Netherlands | KvK 24441791
>
>
>
>
>
>
>
>
>
> From: Jason R. Coombs [mailto:jaraco@jaraco.com]
> Sent: maandag 23 november 2009 11:56
> To: support@sliksvn.com
> Subject: SlikSVN 1.6.6 64-bit stalls on some operations
>
>
>
> Greetings,
>
> I sent a message about this issue via the web support form a
> couple of weeks ago. I didn’t hear anything, so I’m resending in case the
> first message was lost. I also have additional information over what I
> reported before. I’m hoping this issue can be resolved for the next release.
>
>
>
> I’ve been using SlikSVN for all of my 64-bit Windows
> systems. Beginning with 1.6.6, I found that the svn client frequently
> stalls, for 120 seconds or more, on certain operations. It seems to stall in
> particular at the following places:
>
>
>
> 1) At the beginning of a checkout operation, before copying any files.
>
> 2) At the end of an import or checkin operation, after the server has
> completed the transaction, but before the client reports the new revision
> number.
>
> 3) At the end of an list operation, before returning control to the
> parent process.
>
>
>
> I think I’ve seen it stall on an update operation, but many updates complete
> without the stall, so I may be mistaken.
>
>
>
> While the client is stalling, I can check the network connections and see
> that a TCP connection is open to the server, so the problem appears to be
> related to some I/O blocking.
>
>
>
> I’ve seen this problem on five separate installations of SlikSvn 1.6.6 (32-
> and 64-bit) on Windows Vista, Windows 7, and Windows Server 2008. I’ve only
> observed the problem when communicating with my server, which is SVN 1.6.6
> behind Apache 2.2.14 behind IIS and ISAPI Rewrite. I had the same problem
> with the 1.6.5 server, so I upgraded it to 1.6.6 to make sure that wasn’t a
> factor. I haven’t observed this problem with any other server, though I use
> my server most frequently.
>
>
>
> I do not experience the stalls when using the Tigris.org 32-bit svn 1.6.6
> client nor when using TortoiseSVN 1.6.6 (either 32- or 64-bit), so the
> problem seems to be unique to my server and SlikSVN 1.6.6. I’d like to
> continue to use SlikSVN’s client, but these stalls are quite annoying.
>
>
>
> I suspect you will be able to replicate the problem by performing a list on
> https://svn.jaraco.com/jaraco/python/ .
>
>
>
> It’s quite possible the problem is related to my server, but since the
> problem emerged between SlikSVN 1.6.5 and 1.6.6 and because the server works
> reliably with other clients, I’m hoping a solution can be found with
> SlikSVN. I’m happy to run test or debug code and help track down the issue.
> I’ve never compiled an SVN client before, but I have Visual Studio 2008 and
> I’m comfortable working through a procedure to set up the dependencies if
> it’s documented well enough. I didn’t see SlikSVN source code on the web
> site, though, so I understand if you’re keeping that proprietary.
>
>
>
> Please let me know if I can provide an additional information.
>
>
>
> Regards,
>
> Jason R. Coombs
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2432256
Please start new threads on the <us...@subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <us...@subversion.apache.org>.