Return-Path: X-Original-To: apmail-chemistry-dev-archive@www.apache.org Delivered-To: apmail-chemistry-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 156E9174B0 for ; Tue, 24 Mar 2015 21:28:53 +0000 (UTC) Received: (qmail 46915 invoked by uid 500); 24 Mar 2015 21:28:53 -0000 Delivered-To: apmail-chemistry-dev-archive@chemistry.apache.org Received: (qmail 46876 invoked by uid 500); 24 Mar 2015 21:28:52 -0000 Mailing-List: contact dev-help@chemistry.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@chemistry.apache.org Delivered-To: mailing list dev@chemistry.apache.org Received: (qmail 46864 invoked by uid 99); 24 Mar 2015 21:28:52 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Mar 2015 21:28:52 +0000 Date: Tue, 24 Mar 2015 21:28:52 +0000 (UTC) From: "jay brown (JIRA)" To: dev@chemistry.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CMIS-903) Client blocks after multiple removeFromFolder operations MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 jay brown created CMIS-903: ------------------------------ Summary: 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 Priority: Critical Fix For: DotCMIS 0.7 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)