Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 7C5E8200C7D for ; Tue, 2 May 2017 02:22:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 7B07F160BC1; Tue, 2 May 2017 00:22:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A4BC7160BC2 for ; Tue, 2 May 2017 02:22:08 +0200 (CEST) Received: (qmail 4636 invoked by uid 500); 2 May 2017 00:22:07 -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 4625 invoked by uid 99); 2 May 2017 00:22:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 May 2017 00:22:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 56733C11CA for ; Tue, 2 May 2017 00:22:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id AQzhwWBdj4QR for ; Tue, 2 May 2017 00:22:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 049525FB29 for ; Tue, 2 May 2017 00:22:06 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 415D0E0D50 for ; Tue, 2 May 2017 00:22:05 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 68BCD21DEE for ; Tue, 2 May 2017 00:22:04 +0000 (UTC) Date: Tue, 2 May 2017 00:22:04 +0000 (UTC) From: "vinay (JIRA)" To: dev@chemistry.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CMIS-1004) BridgeServiceFactory taking long time MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 02 May 2017 00:22:09 -0000 [ https://issues.apache.org/jira/browse/CMIS-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] vinay updated CMIS-1004: ------------------------ Attachment: ThreadAnalysis.docx Thread Analysis > BridgeServiceFactory taking long time > ------------------------------------- > > Key: CMIS-1004 > URL: https://issues.apache.org/jira/browse/CMIS-1004 > Project: Chemistry > Issue Type: Bug > Components: opencmis-bridge, opencmis-server > Affects Versions: OpenCMIS 1.1.0 > Reporter: vinay > Attachments: ThreadAnalysis.docx, ThreadAnalysis.docx > > > Hi, > We have a query around time taken by BridgeServiceFactory with every request. Below are the details of our implementation. > We have created ServiceFactory class by extending AbstractBridgeServiceFactory and overriding below methods : > @Override > protected FilterCmisService createService(CallContext context) > > @Override > public CmisService getService(CallContext context) > @Override > public void init(Map parameters) : In this method we are enabling ServiceWrapper feature and then calling the super.init() > > We have observed that every SOAP request is taking more than 12 seconds to get the Service (i.e. getService(CallContext context) call) > The overridden getService(CallContext context) method calls CachedBindingCmisService.setCallContext(CallContext context). > Our assumtion was that since cache is in place first request will take time once cache gets warm up. And then all the subsequent call will utilize cache. > But this is not happening and every request builds the cache. > On further investigation we found that CachedBindingCmisService.getCmisBindingFromCache() method always return null. It is because the internal call to HttpSessionCmisService.getCmisBindingFromCache() not able to find the existing session > { > HttpSession httpSession = getHttpSession(false) ---> This always return null. > } > Please let us know if there is way to improve and utilize the inbuilt cache mechanism. Or is it something missing while creating custom ServiceFactory class by extending AbstractBridgeServiceFactory. > Thanks & Regards, > Vinay -- This message was sent by Atlassian JIRA (v6.3.15#6346)