Fixes livelock

[sventorben]

This fixes a livelock when a custom scoped bean depends on another bean of the same scope.

When two beans have the same custom scope and depend on each other (see thread dump in screenshot: CouchDbDatabaseName and MandantLuceneCouchDbConnector), I randomly get a livelock.

This PR should fix this.

[simschla]

is this ever going to be merged?

[simschla]

🥳

[exabrial]

So I was able to randomly reproduce this problem, and I had a setup similar to yours where I had beans of the same scope. However, I think the problem was self-induced

Initially I had:

	@Inject
	@Destroyed(MyCustomScopeScoped.class)
	private Event<Object> scopeDestroyed;
	
	...
	
				context.destroy(newScopeKey);
				scopeDestroyed.fire(newScopeKey); // <-- observed by beans of the same scope
				context.exit(null);

but to fix it, I needed to tear down in this order:

scopeDestroyed.fire(newScopeKey);
context.destroy(newScopeKey);
context.exit(null);

any chance that is your issue?