<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Mon, May 15, 2017 at 12:13 AM Matej Novotny <<a href="mailto:manovotn@redhat.com">manovotn@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">TestScenario1/2 are pretty much what we are discussing here - the container terminates and observers don't get notified any more.<br>
Obviously, if you hang any additional 'thenRun' etc. on top of that, it won't work either.<br></blockquote><div><br></div><div>Right.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">TestScenario3 is with Weld parallel mode and is IMO out of scope of previous discussion but important nonetheless.<br></blockquote><div><br></div><div>Yeah—this git repo was less a reproducer and more just me playing around. :-)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This is indeed weird and I think you are observing a peculiar behaviour of default executor in SE, which is ForkJoinPool.<br>
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.<br>
I think we need to look into FJP to see what's truly going on there.<br></blockquote><div><br></div><div>Oh, that is interesting. OK; thanks.</div><div><br></div><div>Best,</div><div>Laird</div></div></div>