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 E1253200AE4 for ; Fri, 24 Jun 2016 12:54:17 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DE3A0160A5A; Fri, 24 Jun 2016 10:54:17 +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 584D7160A38 for ; Fri, 24 Jun 2016 12:54:17 +0200 (CEST) Received: (qmail 80308 invoked by uid 500); 24 Jun 2016 10:54:16 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 80298 invoked by uid 99); 24 Jun 2016 10:54:16 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Jun 2016 10:54:16 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 1D3942C14F8 for ; Fri, 24 Jun 2016 10:54:16 +0000 (UTC) Date: Fri, 24 Jun 2016 10:54:16 +0000 (UTC) From: "Knut Anders Hatlen (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DERBY-6891) Investigate concurrency improvements to DerbyObservable and DerbyObserver MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 24 Jun 2016 10:54:18 -0000 [ https://issues.apache.org/jira/browse/DERBY-6891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348133#comment-15348133 ] Knut Anders Hatlen commented on DERBY-6891: ------------------------------------------- The patch looks good to me. Now that all the methods synchronize on the DerbyObservable instance, it should be safe to replace the Vector with an unsynchronized ArrayList. > Investigate concurrency improvements to DerbyObservable and DerbyObserver > ------------------------------------------------------------------------- > > Key: DERBY-6891 > URL: https://issues.apache.org/jira/browse/DERBY-6891 > Project: Derby > Issue Type: Improvement > Components: Store > Reporter: Rick Hillegas > Attachments: derby-6891-01-aa-synchronizeMethods.diff > > > As part of derby-6856, we introduced a pair of classes which manage callbacks between classes in the Store layer. The classes are DerbyObservable and DerbyObserver. They replace the deprecated Observer and Observable classes in the JVM and allow Derby to build without deprecation warnings. Right now, callbacks are managed by a Vector. It is quite likely that the concurrency of these classes (and therefore of the Store layer) could be boosted by using some mechanism from java.util.concurrent. -- This message was sent by Atlassian JIRA (v6.3.4#6332)