Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E80F8195FB for ; Wed, 9 Mar 2016 09:05:40 +0000 (UTC) Received: (qmail 66677 invoked by uid 500); 9 Mar 2016 09:05:40 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 66639 invoked by uid 500); 9 Mar 2016 09:05:40 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 66627 invoked by uid 99); 9 Mar 2016 09:05:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Mar 2016 09:05:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id AC2552C1F54 for ; Wed, 9 Mar 2016 09:05:40 +0000 (UTC) Date: Wed, 9 Mar 2016 09:05:40 +0000 (UTC) From: "Yotam Madem (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CXF-6825) Performance bottle neck due to synchronize block on each read MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-6825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186794#comment-15186794 ] Yotam Madem commented on CXF-6825: ---------------------------------- Ok, I see what you mean, If I call to h = THREAD_BUSSES.get(cur); during the operation of clearDefaultBusForAnyThread I can get something that it is about to be removed. > Performance bottle neck due to synchronize block on each read > ------------------------------------------------------------- > > Key: CXF-6825 > URL: https://issues.apache.org/jira/browse/CXF-6825 > Project: CXF > Issue Type: Bug > Components: Bus, JAX-RS > Affects Versions: 3.1.0, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 3.2.0, 3.1.6 > Environment: All environments > Reporter: Yotam Madem > Fix For: 3.2.0, 3.1.6 > > Original Estimate: 24h > Remaining Estimate: 24h > > In our (IBM MobileFirst foundation) performance tests it is possible to see that many threads are stuck at: > "LargeThreadPool-thread-1505" daemon prio=10 tid=0x00007f10f020b800 nid=0x31fc waiting for monitor entry [0x00007f12bfffd000] > java.lang.Thread.State: BLOCKED (on object monitor) > at org.apache.cxf.BusFactory.getThreadBusHolder(BusFactory.java:120) > - waiting to lock <0x00000000c6b99020> (a java.util.WeakHashMap) > at org.apache.cxf.BusFactory.getAndSetThreadDefaultBus(BusFactory.java:202) > > (We use version 3.1.0) > I did a test fix locally and it seems to resolve our problem so I submitted 2 pull requests: > for 3.1.6: https://github.com/apache/cxf/pull/119 > for 3.2.0: https://github.com/apache/cxf/pull/120 -- This message was sent by Atlassian JIRA (v6.3.4#6332)