Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <1010638518.1261571549487.JavaMail.jira@brutus>
Date: Wed, 23 Dec 2009 12:32:29 +0000 (UTC)
From: "Carsten Ziegeler (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Commented: (FELIX-1913) All events are processed in a queue
In-Reply-To: <1618335896.1259743460674.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FELIX-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794034#action_12794034 ] 

Carsten Ziegeler commented on FELIX-1913:
-----------------------------------------

Yes, more or less :) Each event handler is sent the event with a new thread. If you have two event handlers for a given event, the second handler is called either when the first one returns (within the timeout) or as soon as the timeout occurs. In this case the first handler is immediately blacklisted - so a handler is blacklisted as soon as the timeout is reached and other handlers get called immediately.

> All events are processed in a 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, ea2.patch, org.apache.felix.eventadmin-1.0.1-SNAPSHOT.jar
>
>
> The current event admin implementation puts all events into a  queue and processes this queue 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.
> In the async mode, event deliver might take a long time as these events are processed one after the other as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.