felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-1913) All events are processed in a queue
Date Fri, 29 Jan 2010 15:26:34 GMT

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

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

I've attached a new patch (and removed all old ones) - the new one adds one feature which
is in the original implementation: if sync events are sent nested, the timer for blacklisting
a handler is stopped for the outer event while the inner event is sent.

> 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: eventadminfinal.patch
>
>
> 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.


Mime
View raw message