[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Deadlock-like behaviour of svnserve in multi-threaded mode (-T)

From: Tomas Bilek <tomas.bilek_at_polarion.com>
Date: Wed, 16 Nov 2016 00:52:56 -0700 (MST)

Hello Ivan,
I am continuing in topic, which Radek has started previously. I have created
networkdump where you can see communication on localhost. Dump was started
approx 5 s before our application started but is starts using SVN later.
There are relative time stamps. Also I have packed process monitor result
but unfortunetely from time after svn starts hang up, because when I was
running process monitor I was not able to reproduce that problem, so I
turned it on after the system hangs.

To logs.
1) Network (network dump
when i filter only tcp.port = 3690 I see that communication stopped and
there is window from 245s until 637s
and this is snippet from our app log
2016-11-07 12:54:20,753 [ObjectIndex-refreshIndex-1 | u:p] INFO
com.polarion.platform.startup - -- -- 631 from 731 objects were refreshed
2016-11-07 13:00:54,030 [ObjectIndex-refreshIndex-2 | u:p] INFO
com.polarion.platform.startup - -- -- 731 from 731 objects were refreshed
   /////Indexing take some time from 10-20s so the difference 300-400s is

2) Process Monitor (dumps
you can filter at start for svnserve.exe. at start 07.11.2016
13:00:52,5687177 there is "disconnect sequence"

Do you think, that it is enough info to determine, where is the problem?

View this message in context: http://subversion.1072662.n5.nabble.com/Deadlock-like-behaviour-of-svnserve-in-multi-threaded-mode-T-tp196421p197955.html
Sent from the Subversion Dev mailing list archive at Nabble.com.
Received on 2016-11-16 08:53:03 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.