You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 7, 2020. It is now read-only.
There are reports where the OSGiEventManager gets blacklisted by the OSGi EventAdmin, which results in an unusable system state. Instead of being blamed, the OSGiEventManager should instead make sure to identify blocking handlers itself and return quickly.
The text was updated successfully, but these errors were encountered:
Even if it would take such buggers out of the game, I still see two remaining problems:
The default timeout of e.g. felix event admin is 5s, which is exactly the timeout of the safe method caller in this case. So at the point where it identifies a slow event subscriber, it is already to late and the event manager got banned itself.
If the internal timeouts are fixed, then the same would arise if there are multiple slow subscribers because they are informed serially.
The "proper" solution I guess would be to inform the subscribers asynchronously completely (and thereby taking care to ban slow subscribers itself). Wdyt?
* remove "hanging" event subscribers from the game
* inform _all_ event subscribers asynchronously
fixeseclipse-archived#4591
Signed-off-by: Simon Kaufmann <[email protected]>
There are reports where the OSGiEventManager gets blacklisted by the OSGi EventAdmin, which results in an unusable system state. Instead of being blamed, the OSGiEventManager should instead make sure to identify blocking handlers itself and return quickly.
The text was updated successfully, but these errors were encountered: