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 https://drive.google.com/file/d/0ByHPI8jVgwP8ZHJxbHZ5Z3BScVU/view?usp=sharing) 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 (86%) 2016-11-07 13:00:54,030 [ObjectIndex-refreshIndex-2 | u:p] INFO com.polarion.platform.startup - -- -- 731 from 731 objects were refreshed (100%) /////Indexing take some time from 10-20s so the difference 300-400s is corresponding. 2) Process Monitor (dumps https://drive.google.com/file/d/0ByHPI8jVgwP8Qm0xa1ExNEQxZFU/view?usp=sharing) 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.
