You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by "Florian Müller (JIRA)" <ji...@apache.org> on 2015/03/30 17:21:52 UTC
[jira] [Commented] (CMIS-903) Client blocks after multiple
removeFromFolder operations
[ https://issues.apache.org/jira/browse/CMIS-903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14386853#comment-14386853 ]
Florian Müller commented on CMIS-903:
-------------------------------------
There is a fix in trunk, now. Please retest with your server before I close this issue. Thanks.
> Client blocks after multiple removeFromFolder operations
> --------------------------------------------------------
>
> Key: CMIS-903
> URL: https://issues.apache.org/jira/browse/CMIS-903
> Project: Chemistry
> Issue Type: Bug
> Components: dotcmis
> Affects Versions: DotCMIS 0.6
> Reporter: jay brown
> Assignee: Florian Müller
> Priority: Critical
> Fix For: DotCMIS 0.7
>
> Attachments: IBMTest.cs, Program.cs
>
>
> We found a situation where the client iterates through a list of documents in a folder, unfiling them one by one. (Atompub 1.0 binding)
> After the second iteration the client will hang and timeout. (server is ok)
> Increasing the .Net runtime's ServicePointManagerDefaultConnectionLimit
> docs here
> https://msdn.microsoft.com/en-us/us-en/library/system.net.servicepointmanager.defaultconnectionlimit.aspx
> from default of 2 to X will move the problem to iteration X. (i.e. increase to 10 and hang will happen on iteration 10)
> Reproduced this with FileNet server and with inMemory server to verify it was not something vendor specific we were doing.
> Will attach sample .net client code in case you need to reproduce this locally. See LOOK_HERE label in sample code for exaction location of hang.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)