Return-Path: Delivered-To: apmail-felix-dev-archive@www.apache.org Received: (qmail 14871 invoked from network); 3 Dec 2009 10:10:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Dec 2009 10:10:45 -0000 Received: (qmail 92382 invoked by uid 500); 3 Dec 2009 10:10:44 -0000 Delivered-To: apmail-felix-dev-archive@felix.apache.org Received: (qmail 92304 invoked by uid 500); 3 Dec 2009 10:10:44 -0000 Mailing-List: contact dev-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@felix.apache.org Delivered-To: mailing list dev@felix.apache.org Received: (qmail 92294 invoked by uid 99); 3 Dec 2009 10:10:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Dec 2009 10:10:44 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Dec 2009 10:10:42 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 3368E234C052 for ; Thu, 3 Dec 2009 02:10:21 -0800 (PST) Message-ID: <2010578416.1259835021209.JavaMail.jira@brutus> Date: Thu, 3 Dec 2009 10:10:21 +0000 (UTC) From: "Carsten Ziegeler (JIRA)" To: dev@felix.apache.org Subject: [jira] Commented: (FELIX-1913) All synchronous events are processed in one queue In-Reply-To: <1618335896.1259743460674.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/FELIX-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785247#action_12785247 ] Carsten Ziegeler commented on FELIX-1913: ----------------------------------------- I'Ve attached a prototype for an improvement - it is clearly not the final solution. I've changed the thread pool to work with plain Runnable's and then just changed the execute method of the sync handler: the event handlers are processed one after the other. If no timeout is set, the handlers are called directly If a timeout is set, the handlers are called by a thread from the thread pool and blacklisting is also handled. This allows to process events in parallel when they come from different threads. I did some basic tests and it seems to work (incl. blacklisting etc.) > All synchronous events are processed in one queue > ------------------------------------------------- > > Key: FELIX-1913 > URL: https://issues.apache.org/jira/browse/FELIX-1913 > Project: Felix > Issue Type: Improvement > Components: Event Admin > Affects Versions: eventadmin 1.0.0 > Reporter: Carsten Ziegeler > Assignee: Karl Pauls > Priority: Minor > Attachments: ea.patch > > > The current event admin implementation puts all events into one single queue and processes this queue is in one thread. This creates a bottleneck when different threads send events as they have to wait for other threads to be processed first. Events from different threads can be processed in parallel. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.