aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Cabrera (JIRA)" <>
Subject [jira] Reopened: (ARIES-12) BlueprintListener events are not delivered synchronously
Date Fri, 02 Oct 2009 13:32:23 GMT


Alan Cabrera reopened ARIES-12:

There are still the other issues that I mentioned.  One still has to do with the fact that
events are still not delivered synchronously since there's a thread pool in the dispatcher.
 The other is most likely a new issue that needs to be filed.

Please comment.

> BlueprintListener events are not delivered synchronously
> --------------------------------------------------------
>                 Key: ARIES-12
>                 URL:
>             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.

View raw message