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 8C3F710938 for ; Mon, 8 Dec 2014 08:54:01 +0000 (UTC) Received: (qmail 14918 invoked by uid 500); 8 Dec 2014 08:54:01 -0000 Delivered-To: apmail-chemistry-dev-archive@chemistry.apache.org Received: (qmail 14863 invoked by uid 500); 8 Dec 2014 08:54:01 -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 14852 invoked by uid 99); 8 Dec 2014 08:54:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Dec 2014 08:54:01 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [80.241.56.68] (HELO plasma6.jpberlin.de) (80.241.56.68) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 08 Dec 2014 08:53:53 +0000 Received: from gerste.heinlein-support.de (gerste.heinlein-support.de [91.198.250.173]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by plasma.jpberlin.de (Postfix) with ESMTPS id 9FBEAAD333; Mon, 8 Dec 2014 09:53:32 +0100 (CET) X-Virus-Scanned: amavisd-new at heinlein-support.de Received: from plasma.jpberlin.de ([91.198.250.140]) (using TLS with cipher AES256-SHA) by gerste.heinlein-support.de (gerste.heinlein-support.de [91.198.250.173]) (amavisd-new, port 10024) with ESMTPS id P67C0o3twB6W; Mon, 8 Dec 2014 09:53:31 +0100 (CET) Received: from webmail.jpberlin.de (sinatra6.heinlein-hosting.de [91.198.250.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: fmueller@jpberlin.de) by plasma.jpberlin.de (Postfix) with ESMTPSA id 21E53AD3A3; Mon, 8 Dec 2014 09:53:30 +0100 (CET) Received: from roZ35rh+T/lxqmT6fzmhvqQPQ1TOH7JQpEf/PGOTWwE= (vgK58Isxr+/N7N4SQLBmFY3rDH6oR3Ka) by webmail.jpberlin.de with HTTP (HTTP/1.1 POST); Mon, 08 Dec 2014 09:53:30 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 08 Dec 2014 09:53:30 +0100 From: =?UTF-8?Q?Florian_M=C3=BCller?= To: dev@chemistry.apache.org Cc: wt lu Subject: Re: how to increase timeout for opencmis bridge In-Reply-To: References: Message-ID: <669a77c386e6c53417a973ba4f285845@jpberlin.de> X-Sender: fmui@apache.org User-Agent: RoundCube Webmail X-Virus-Checked: Checked by ClamAV on apache.org Hi Wentao, It depends on how you set up the bridge and if you add your own code that manages the sessions to the backend. If you are using the SimpleForwardingCmisService class that comes with the brdige, then the two lines should look like this: forwarding.binding.org.apache.chemistry.opencmis.binding.connecttimeout=60000 forwarding.binding.org.apache.chemistry.opencmis.binding.readtimeout=60000 - Florian > we are using opencmis bridge to forward third party cmis client request > (DotCMIS) to backend CMIS server. > > intermittently we saw timeout error in opencmis bridge logs when the > bridge > forward the request to CMIS server, Still need to figure out why it's > timeout but I guess we can first try to increase it. > > Should I just add these two lines in > the WEB-INF\classes\repository.properties file? > > org.apache.chemistry.opencmis.binding.connecttimeout = 60000 // i.e. 60 > sec > org.apache.chemistry.opencmis.binding.readtimeout = 60000 // i.e. 60 > sec > > > > Thanks > Wentao