felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Pauls (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FELIX-1913) All events are processed in a queue
Date Wed, 23 Dec 2009 13:02:29 GMT

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

Karl Pauls commented on FELIX-1913:

So how do you handle timeouts in the case of stacked sync events then? Are you still preserving
the order in that case? I guess i will have to find my old tests and look at your patch. I'll
give it a go and report back next week. 

> 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.

View raw message