On 10 Feb 2015, at 02:13, Hermann Gábor <reckone...@gmail.com> wrote:
> Hey Ufuk, > > Thanks for the fast reply and fix! It's working now :) > > Unfortunately the "other side" of the AbstractInvokable lifecycle is > causing a bit of a trouble, > as the AbstractInvokable does not wait for possible events before > finishing, and it throws an > IllegalStateException: Tried to send task event to producer before > requesting a queue. > exception when trying to send an event after the task finished. > > For now we have a workaround to this (the above fixed problem was the > trickier one for us) in a higher level, but it would be > nice if the events adjusted to the AbstractInvokable lifecycle, i.e. the > AbstractInvokable would be kept up > until all Readers/Writers that subscribed to events are shut down. OK, good to hear that it is working. The producer and consumer tasks used to wait for each other before they finished. With iterations and superstep events, the iteration task logic ensures that tasks don't finish prematurely. How are you doing it? Waiting a certain number of events?
