[
https://issues.apache.org/jira/browse/ARIES-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick McGuire closed ARIES-12.
-----------------------------
Resolution: Invalid
Ah, I missed the point that this was using the single thread executor. My
original reading was that the event dispatch would get handled currently on
multiple threads because it was using the ExecutorService.
> BlueprintListener events are not delivered synchronously
> --------------------------------------------------------
>
> Key: ARIES-12
> URL: https://issues.apache.org/jira/browse/ARIES-12
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Reporter: Rick McGuire
> Assignee: Alan Cabrera
>
> Section 121.12 of the blueprint specification has a requirement that
> blueprint events be delivered to BlueprintListener.blueprintEvent() methods.
> However, the implementation of the event dispatcher submits the callbacks for
> each event to an executor for processing, leading to race conditions where
> events can be delivered out of order. These events really should be placed
> on a queue and all callbacks completely processed in order.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
