[
https://issues.apache.org/jira/browse/FELIX-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12785281#action_12785281
]
Karl Pauls commented on FELIX-1913:
-----------------------------------
Well, as you discovered, and as I already mentioned, the issue is that you have
to make sure that events are observed in the right order (including the
stacking of events) on a per thread basis. I was thinking that you where
talking about the case of parallel delivery of the same event. I agree that you
should be able to deliver events from different threads in parallel.
Just make sure that for each parallel thread you do the right thing if it comes
back into the ea (i.e., stacks a new event) even if you use a new one from the
thread pool.
> 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.
