[cdi-dev] What, if any, guarantees are made about invoking asynchronous event observer methods?

Laird Nelson ljnelson at gmail.com
Mon May 15 11:25:10 EDT 2017

On Mon, May 15, 2017 at 12:13 AM Matej Novotny <manovotn at redhat.com> wrote:

> TestScenario1/2 are pretty much what we are discussing here - the
> container terminates and observers don't get notified any more.
> Obviously, if you hang any additional 'thenRun' etc. on top of that, it
> won't work either.


> TestScenario3 is with Weld parallel mode and is IMO out of scope of
> previous discussion but important nonetheless.

Yeah—this git repo was less a reproducer and more just me playing around.

> This is indeed weird and I think you are observing a peculiar behaviour of
> default executor in SE, which is ForkJoinPool.
> We have a test[1] for parallel execution in SE, where we defined your own
> executor (see 'createWeld' method) and it works like a charm.
> I think we need to look into FJP to see what's truly going on there.

Oh, that is interesting.  OK; thanks.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20170515/0566d36f/attachment.html 

More information about the cdi-dev mailing list